PROBLEMCHYLD

Here is the list for Unofficial Windows 98 Second Edition USB Stack 1.x + 2.x. It will be its own executable and will install with Main Updates to the Windows\System folder. You will have to manually run the file USBSTACK.EXE. I will either have it ready by the weekend or early sometime next week. If users have any problems with USBSTACK.EXE, please post in this forum because it is a counterpart of U98SESP3.x. 1394.INF HIDCLASS.SYS 5.0.2195.6882 HIDDEV.INF HIDPARSE.SYS 5.1.2600.5512 HIDUSB.SYS 5.1.2600.5512 HIDVKD.SYS 4.90.0.3000 NODRIVER.INF OPENHCI.SYS 4.90.3000.0 UHCD.SYS 4.90.3000.0 USB.INF USB2.INF USBAUTH.SYS 4.90.3000.0 USBD.SYS 4.90.3000.0 USBCCGP.SYS 5.1.2600.5585 USBCDC.INF USBDSC1.SYS 4.10.0.1998 USBDSC2.VXD 4.0.0.950 USBEHCI.SYS 5.0.2195.6882 USBHUB.SYS 5.0.2195.7006 USBHUB20.SYS 5.0.2195.6891 USBMPHLP.PDR 4.90.3000.0 USBNTMAP.INF USBNTMAP.SYS 4.90.0.3000 USBPORT.SYS 5.0.2195.6941 USBSER.SYS 5.1.2600.5512 USBSTOR.INF USBSTOR.SYS 5.0.2195.6773 USBU2A.SYS 1.4.2.0 USBVIEW.EXE 5.1.2600.2180 WDMSTUB.SYS 5.0.0.6 X360C.INF X360C.SYS 5.2.3790.1830 X360HORI.INF X360MDCZ.INF X360CCP.DLL 5.2.3790.1830 X360CFF.DLL 5.2.3790.1830 X360CSA.EXE 5.2.3790.1830

I never witnessed this either but I did get BSODs on a clean install with my infrared device enabled. I know for a fact it was cause by files from USB drivers. And my IR is on COM. I was using Win98 only USB files not WinME or Win2000 files and still got the BSOD. I had to disable my IR device. I'm starting to think the USB drivers are NOT the problem but certain hardware using the resources thats needed by USB. I never had a reason until now to use my infrared and its conflicting with my other hardware. I think users are always going to have this problem. After some research and reading many posts, the problems lies with the hardware. This is why some of us get BSODs and some of us don't. We probably should start looking into how to patch the files. I can confirm BSODs with my infrared with all version of USB files, Win98, WinME, 2000, XP. It didn't matter.

The USB drivers also conflicts with my infrared devices. I will have to remove them until further notice. I can't even disable them from installing because new hardware will pull the newer files from the SP3 cab. I will just remove them completely. People are having problems with NUSB also. Sorry guys. The file DISKTSD.VXD from MDGx IOSYS98.EXE and DISKTSD.VXD from Maximus-Decim Native USB Drivers have the same version number but different CRC32 hashes. This might be one of our problems. I will create a separate pack and call it Unofficial Windows 98 Second Edition USB Stack 1.x + 2.x. I will also add the XBOX 360 USB drivers and remove them from the SP3. I'm removing SP3 links to avoid system BSODs. Thanks guys for testing

I'll send you a link once I finish packaging. Thanks GUTILS.DLL 5.2.3790.0 Vista Platform SDK SMCIRDA.INF SMCIRDA.SYS 4.10.1999.5 WINDIFF.CHM Vista Platform SDK WINDIFF.EXE 6.0.6000.16384 Vista Platform SDKI have decided to leave the USB 1.x/USB 2.0 in SP3 My goal is to find a solution to the problem not cover it up. If we can barely get the USB 1.x/USB 2.0 drivers working properly, then we don't stand a chance @ USB 3.0, Windows Portable Devices (WPD), Media Transfer Protocol (MTP) and whatever newer technology comes our way. I've learned that the decision I have made will not suit everyone. I've also learned that removing the drivers will also no suit everyone. There is a win - lose situation here and since the majority is not having problems, I'm in their favor. I will add notice to users with VIA controllers. What I will do is continue to try and find a solution, since I don't have any VIA devices, it going to be a while.

@ dencorso If you can be so kind and do me a small favor if you have the time. I would like you to test USBHUB20.SYS 5.0.2195.6891 with and without WDMSTUB.SYS/WDMEX.VXD. Neither one is needed to run USBHUB20.SYS 5.0.2195.6891, but it might help me pinpoint some problems and hopefully figure out a solution. Also if you find that the lastest version of WDMSTUB.SYS might be the culprit, can you try using a older version posted in your quote below. Thanks if you do and thanks if you don't

Sorry guys, but there is NO DRIVERS for Win98. Its ok if people don't believe that and want to keep searching, but please considerate of others. Having people search for a driver that doesn't exist is.................................. Thank you LoneCrusader for finding an older driver. This shows that no matter how far you go there was no win98 drivers.

I'm sorry for your troubles This is the only hardware I have that doesn't have a Win98 driver. So far, no one has proven me wrong. Its ok to be right sometimes.

There will be many opinions about whats a good pack to use. Its up to you to find out what suits your needs. SP3 has a few flaws, but what software doesn't? Regardless, if another user doesn't recommend something, use your own discretion. Its not about what another user like or feel, but how you feel and what you like. People complain about MS software all the time, but they continue to use it. If I were you, I would install each pack separately and see whats best for you. The SP installs over 900+ files and most of the files are optional. There is about 100+ not optional (some updated files DON'T exist on Win98) and becuase most are runtime libraries. Most people don't have problems with SP3 and I don't use Virtual Machines so I can't test your problem. Here a little example, I don't use Microsoft Vista, I have tried it and didn't like it. Just becuase I didn't like it, doesn't mean I shouldn't recommend it to others. Thats weirdo $h!+

Merry Christmas everyone and may you be blessed with many more.

If you guys can recommend a VIA pcmcia card I'll buy one over the holidays. This will allow me to test Nec, Intel and the Via all at the same time when I get it. I think pushing the problem to the side and covering it up is not the ideal solution. I will take all suggestions into consideration.

Shuffling the drivers around won't do any good because people who have certain chipsets will still have problems. Optional or not, the issue remains at hand. Thanks for the feedback.

Its the same story, but told in a different way. We all still suffer

I have learned a lot from you. I will cherish it til the day I die. I'm hoping we will get a flawless SP. This is my goal, this is my ambition. With your help and others, I think we will make it, hopefully. Its crazy how someone can be so kind, but yet be still so vicious I don't mean to be. My demeanor can be a double edged sword. I have been chosen to learn the hard way

I know what you mean The elders use to tell me I was young with an old soul. I know exactly what that means. They told me I was wise for my age even though I have a temper lol

If I get rich, I will be looking for you. I have the same love for you as my own flesh and blood. I consider you family and it will always be that way because of your kind words. We don't always agree, but together we will prosper

I beg to differ. The reason being, if you really want something done, you can do it. I wanted an updated SP, when nobody stepped up to the plate [i did] with you guys help. I did it because I love Win98. I didn't gain anything but a updated system, invested countless days and learned a new skill which I lacked but desired. If I had to do it all over again, I would, because I'm passionate. I don't make excuses, I make solutions. I have the drive, that anything I'm ambitious about, I'm going to succeed at it. Thats just me. If you aint willing to sacrifice something, then you will end up with nothing. A very big thank you Drugwash, because you have done more than just chipped in.

My biggest problems with some testers is, when they have problems they don't look for solutions or work arounds. All of my USB controllers are Intel/Nec, so I understand where you are coming from. I also the love the fact that you are always mutual in your replies I can understand some people not able to sacrifice their systems for whatever reasons, but what about the people who can? Is it that hard to back up a system, format the drive and do a clean install of win98 with the SP I do it all the time before a new release. If everything works fine, you can actually build off the new installation. Hey, that may be too much like right I also feel removing USB drivers is a step backwards, but it also hinders us moving foward. I want the SP to be complete, in other words 10 years from now, a clean windows install with SP, one should have a fully updated system. I won't turn my back yet, but when it becomes a losing battle, I'll have to wave the flag

I have some Good news and Bad news. I will release 2 versions of SP sometime in January. It will be a 3.14 and a 3.15. SP 3.14 wil be the last version with USB support. I will remove all USB drivers from 3.15 and above. It seems that the USB drivers are causing conflicts on different systems even though they work on many other systems. Its seem no one is interested in coming up with a overall solution, which means many are content with the situation as long as it don't [affect/effect] them. So I'm content as well I said this before, I don't think people should use VIA drivers with Intel, Sis drivers with NEC etc.... I tried to use MS only drivers as a universal solution, it didn't work out so nicely That means if you have had problems with NUSB and the SP3.x USB 1.1/USB 2.0 drivers, I don't have a solution for you. I will not waste my time trying to update 2 packages. Its not worth it

Ok, thanks. I will release 3.14 after New Years with updated files.

So that means the Win98 version of OPENHCI.SYS has a conflict with ATI controllers. Thanks

Are you using a USB mouse or Keyboard? If so you need to use a PS/2 mouse and KB until you get the drivers in place.

You are not suppose to use the via inf file. All you need to do is replace that one file I listed and follow the rest of the usb instructions.

Download this Package Delete SP3.CAB in Windows\System\Precopy. Replace USBHUB20.SYS 5.0.2195.6891 with the VIA version USBHUB20.SYS 4.90.3000.11. Remove all USB drivers in safe mode. Let everything re-detect on start up. Report back here.

It does, I was just being lazy. It was System Restore.The system hive is placed inside a .cab file in the _Restore folder. If you notice the change in the file sizes I posted above, it lets you know system restore has written new data. I only made minor changes, to speed up the process.

I have found and added extra security. If you go to this site Pop-Up Window Killer and scroll down to Pop-Up Window Killer vb script. This is great security for kids. After you have downloaded the PUK.VBS start it, a PUK.TXT will be created. Add whatever filter name [Example] cats to the PUK.TXT file and do a google search for cats. Your browser will close immediately. If you have multiple tabs the script will hang.