PROBLEMCHYLD

dencorso, Whenever you have some free time can you update USBSTOR.INF with the updates from the link below? Here are some new devices that can be added hopefully. ; ; EUIOSSM.INF --- SCM Microsystems Inc Win9x USB SmartMedia Port Driver INF ; ; Copyright (C) SCM Microsystems Inc 1998-1999 ; [Version] signature="$CHICAGO$" Class=SCMUsbMass Provider=%SCM% [ClassInstall] AddReg=SCMUsbMass.AddReg [SCMUsbMass.AddReg] HKR,,,0,%SCMUsbMass% HKR,,Icon,0,-20 [Manufacturer] %SCM%=SCM [SCM] %USB_PDR.DeviceDesc% = euiossm, *PSCMEUSBSMPDR [DestinationDirs] DefaultDestDir = 12 [SourceDisksNames] 1=%DISK1%,, [SourceDiskFiles] euiossm.pdr=1 [euiossm] AddReg = euiossm.AddReg CopyFiles = euiossm.CopyFiles [euiossm.CopyFiles] euiossm.pdr [euiossm.AddReg] HKR,,DevLoader,,*IOS HKR,,PortDriver,,euiossm.pdr [Strings] SCM="SCM Microsystems" SCMUsbMass="USB Port driver" DISK1="eUSB Driver Disk" USB_PDR.DeviceDesc="eUSB MSD Adapter" ; ; EUSBSM.INF - INF file for SCM Microsystems Inc eUSB SM Products ; ; Currently defines eUSB SSFDC ; ; Copyright (C) SCM Microsystems Inc. 1998-2000 ; [Version] signature="$CHICAGO$" Class=USB ClassGUID={36FC9E60-C465-11CF-8056-444553540000} Provider=%SCM% [DestinationDirs] DefaultDestDir = 11; // LDID_SYS EUsbSm.CopyFiles = 11; // %windir%\system UsbPdr.CopyFiles = 12; // %windir%\system\iosubsys PdrInf.CopyFiles = 10, INF\OTHER; [SourceDisksNames] 1=%DISK1%,, [SourceDiskFiles] eusbsm.sys=1 euiossm.pdr=1 euiossm.inf=1 [Manufacturer] %SCM%=SCM.Section [SCM.Section] %USB\VID_04E6&PID_0003.DeviceDesc%=EUsbSm.Dev, USB\VID_04E6&PID_0003 [Start] HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup,%Startup%,,"%01%\..\LAUNCH.EXE" [EUsbSm.Dev] AddReg = EUsbSm.AddReg,Start CopyFiles = EUsbSm.CopyFiles, UsbPdr.CopyFiles, PdrInf.CopyFiles [EUsbSm.AddReg] HKR,,DevLoader,0,*ntkern HKR,,NTMPDriver,0,eusbsm.sys [EUsbSm.CopyFiles] eusbsm.sys [UsbPdr.CopyFiles] euiossm.pdr [PdrInf.CopyFiles] euiossm.inf [Strings] SCM="Microtech International" USB\VID_04E6&PID_0003.DeviceDesc="ZiO SmartMedia Adapter" DISK1="eUSB Driver Disk" Startup="Installing"

I think what I'll do is, just add the VIA-Base driver. That way, all that has to be done while already in safe mode is delete the obsolete driver. I'll have to get the latest driver. If anybody have the lastest VIA driver, please send it to me or post it. I been doing this for a while now so I thought I would post it. I have a NEC USB 2.0 PCMCIA adapter. It requires the OrangeWare USB 2.0 drivers, but I don't need or have them installed. The service pack took care of the issue by using NUSB which uses the file USBEHCI.SYS 5.0.2195.6882. I will leave the MDAC option alone even though it works just to be safe.

Can a vb script be created to detect a chipset or will I need a 3rd party app. I will add the VIA chipset in the next version.

You should be Golden now

Symantec AV 9 is your problem. Disable it. I did some research on your error message, and its cause by any (AVG/ VIRUS SCANNER)! Glad you up and running.

This is what VCACHE.VXD does and it is stable. It has been included in the Service Pack for a while now, before I started to update it.

Thats because I'm using Xeno86 patched VCACHE.VXD and MaxPhysPage 40000 was considered the best setting. Are you using rloew Ram patch? Never had these problems. Let wait and see if others are having the same problems. Its already included. You don't need to install it again.

Can anyone update the files to read 3.1

Great idea. Sometimes it better to pick up where others left off.

The Final update is here. Thanks to MSFN and all its members. This has been a great experience for me. I have learned many things along the way that will follow me for the rest of my life. Please take the time to fully read and understand the homepage for the service pack. Any questions can be posted here and will be answered here. Please note, (ALL) other versions before FINAL are obsolete.

512 MB

I have made notice about MDAC in the new update. You can actually install (ALL) options except MDAC without any errors.If someone does get errors, its probably from not following instructions. Now that the Service Pack is done, I will add all the software I use to my own copy of the service pack. I really enjoyed working on this. I'm ready for a new task. Will upload new version later today.

I see absolutely no problem with having to install MDAC separately. Please don't delay the release of the final build just to resolve this "problem", as it's easily worked around! I'm not going to delay the release, that would be selfish. Although some people might feel once they have the final version, there will no need to find a solution.

I used the Start /W Wait 15 secs and still no luck. It only happens with MDAC. But if I can't find a fix, everyone will just have to install it separately from the other options.

I tried one of the WAIT programs, the results are the same. I think what I need is a program that frees up memory. When you select all options I'm sure the memory takes a huge leak when installing mdac. All other files installs without any issues. The WAIT program did ok, but all it did was prolong the installation about an extra 85 seconds. Someone please recommend a freeware memory tool.

All I need to do is add the wait commands in the inf files.

You are right Fred. I will need to add the small file plus command. I should add the Start /W Wait 4 after every option right or do I add it before?

Thanks Fred I have been testing the MDAC option and it must be installed separately. There is no work around or fix. I have done about 4 installations today. Mdac will corrupt the registry if its not installed by itself. I am done, the final version is finished. I will test some more after I eat dinner.

Well, I have already removed the shell swap option in the final build.

These 2 updates are included, they install with IE Core Files kb905495 - Hotfix for Vulnerability in the Windows FTP Client kb886677 - Unofficial Hotfix for DBCS Corruption in MLANG.DLL I will add MSIEFTP.DLL 5.50.4956.500 to main updates since it doesn't require IE at all. All the updates besides Internet Explorer/Outlook Express updates are included. They only install if they are present on the system. Some files don't need to be on the system if you have no purpose for them. They are all included in SP3.CAB.

The post wasn't directed at you personally. It was directed at anyone who don't follow instructions. It good to hear we are on the same page and you understood where I was coming from.

The final version will be release Monday, April 23, 2012. It was more of an tweak than enhancement. Not in this package. This service pack has nothing to do with anything Quick launch related. When installing MDAC, it eats up all the memory. I have tried different combinations of installations with the same results. I believe its a memory leak. The only way I know how to fix it, is to install Mdac separately from all the other options. I have removed the Win95 shell swap option in the final build.

Service Pack 3 won't let you down.

Now I see why people are having trouble with the service pack. Some people are too lazy to back up their systems. Some people are too lazy to try the service pack on a clean install. So when the problems occur, due to negligence, it's not my fault. I don't even test SP3 with SP2 because of all the changes. I have invested 8 months day and night to get where I'm @ with the service pack. I can handle constructive criticism and negative feedback. What I can't handle is people not following instructions by not reading the fine print. I have never heard the term until dencorso posted it. PEBCAK. It's been posted many times not to mix these packages with each other. Unofficial Windows 98 SE Upgrade Pack (WUPG) Dozen Afterlife Edition November 2010 Unofficial Windows 98 SE Auto-Patcher v2.60 Unofficial Windows 98/98 SP1/98 SE/ME Power Pack (W9xPP) 5.01 Unofficial Windows 98 SE Service Pack 2 (SP2) Can you list the drivers for your device so it can be added to the USB files? Thank you for testing on a clean install.When I release the final version Monday, it should be smooth sailing.

Thanks Fred, but it only happens on MDAC. I 've been reading online about mdac memory leak. I believe mdac has to be installed by itself. I 'll try the links you gave and see what happens. Thanks again.