- This topic is empty.
11. February 2008 at 3:52 #924
I need to install MDAC 2.8 SP1 on to a new build I am creating from the Latest Wyse Firmware on my S90’s.
However the MDAC you download from Microsoft does not install on XPe/XP as it already ships with MDAC.
I have followed the instruction in the MS KB899861 that advises to install using the mdac.inf file, as this did not exist I copied it form my XP PC alond with the i386 and some extra files the installation complained about.
It now runs without error however it does not install.
I know it can be installed as it was installed onto our original build with XPeSP1 however I am unable to locate an installation package that was used back then.
Has anyone done this?11. February 2008 at 6:53 #11666
I did this recently and you need to install the ODBC applet and components along with the Jet DB components. I will find the files and post in the XPe section soon,
-TT13. February 2008 at 23:39 #11701
I have contacted Wyse, and they have gven me an installable MDAC2.8 which appears to work. I am currently testing this.
Many thanks14. February 2008 at 3:02 #11702
Was it just the Jet .DLL’s or the entire MDAC_TYP.EXE?
-TT14. February 2008 at 23:34 #11719
It was the MDAC_TYP.exe
My devlopers still are to test but at least I am only getting a DB permissions error so it appears to be attemptiong to access the SQL table. before the MDAC it just complained about not having MDAC at all.
All I need to do now is physically visit 100 sites to re image all the S90’s we have a PXE and a 512MB image will not work to well over 256 and 512kb ADSL links 😥
you get that
MV15. February 2008 at 2:02 #11720
I still think you may be missing a few peices. Let me post my script and maybe you can avoind PXE and imaging and just push a 6MB package 🙂
-TT15. February 2008 at 2:03 #11721
BTW – what is the Build number of the S90 firmware ❓15. February 2008 at 10:41 #11725
Here you are:
This installs ODBC and MDAC 2.8.SP1 on XPe SP2. This is a WDM package and can be pushed out to all your terminals. Anyone else trying to install an application that needs ODBC, JET database or other DB components will find this useful. .NET 2 also needs this installed first.
Let me know if you have any problems, the package requires a Wyse Windows XPe SP2 image,
-TT18. February 2008 at 1:25 #11741
Our App requires .Net 1.1 will this be enough? it’s slow enough would prefer to not have to install another service.
We are reimaging so that we get the File Based write filter on all the devices this is also updating the firmware.
current existing firmware is 1.10, the reimage upgrades to 1.15 for which I think I have found a small bug.
issue: we are using a USB proximity card reader, when this is installed it works fine however, if you reboot the unit the USB HUB does not reset and the unit essentially crashes and is no longer able to read cards, when the unit resets the USB HUB does not power off and reset. to work arund the issue you need to power off the unit and all will be fine.18. February 2008 at 2:41 #11742
Yes, this should be enough to get .NET up and installed.
When you say the USB hub has to be re-set do you mean the smart card reader is no plugged into the S90 unit directly?
-TT18. February 2008 at 8:30 #11745
The card reader is directly connected to the internal USB hub/bus via one of the USB ports. sorry for the confusion.
When the system restarts normally the LED (power) would go out when the unit resets, as our units are set for Always on in the BIOS a shutdown occurs but the system restarts again and the LED does not go out.18. February 2008 at 11:47 #11748
As a workaround maybe stick to the old BIOS?
To stop this updating on the WDM/WSI server go to the ftprrot/rapport/tools/sa/9S90 folder and open the file push.i2c and edit the line = to be:
This will prevent the BIOS upgrading until you get a resolution,
- You must be logged in to reply to this topic.