pangoomis Posted November 17, 2014 Posted November 17, 2014 ACPI causes some problems based on my experience, mostly on newer computer never made to run Win98SE at all, it causes the setup to crash at the PnP detection section, when installing it on a pendrive. (not from, but on, that's a huge difference) The system on APM operates/shuts down/boots up just as well as with the ACPI.
PROBLEMCHYLD Posted November 17, 2014 Posted November 17, 2014 Most manufacturers install their own 3rd party hibernation applications. Me personally, whenever I buy a new computer, I strip it clean of all Diagnostics, System Utilities, Management software etc....I wonder if the people that have had problems with ACPI, was it due to 3rd party software or Win98 not being updated with the latest hotfixes?
schwups Posted February 9 Posted February 9 That's probably what you're looking for: https://web.archive.org/web/20210722053944/http://www.mdgx.com/files/USB20DRV.EXE (https://web.archive.org/web/20210506185314/http://www.mdgx.com/files/) 1
SweetLow Posted February 15 Posted February 15 (edited) JFYI. much modern version of this pack is available now: http://sweetlow.orgfree.com/download/usb20_win9x.zip Edited February 15 by SweetLow 1
pangoomis Posted February 19 Posted February 19 (edited) On 2/15/2025 at 1:25 PM, SweetLow said: JFYI. much modern version of this pack is available now: http://sweetlow.orgfree.com/download/usb20_win9x.zip The download link does not work under Chromium based browsers as I've mentioned in the past. Let's Encrypt too hard for you? EDIT: Site now works normally and no workarounds are needed. Edited February 21 by pangoomis
jumper Posted February 19 Posted February 19 Remove the filename to get to the download folder, then click the link. Create a new topic on how Let's Encrypt is relevant to the Chromium problem.
SweetLow Posted February 20 Posted February 20 On 2/19/2025 at 9:44 AM, pangoomis said: The download link does not work under Chromium based browsers as I've mentioned in the past Ok, I answer 1. If you are using (bul*****) browser which is literally violating Internet standards - it is YOUR problem. 2. But even in such case there IS workaround: Copy link and past it into address line and if you will get error - reload once again.
pangoomis Posted February 20 Posted February 20 (edited) Thank you, the workaround works, although it is not intuitive, hence I forgot about it and went a bit more angry than necessary, I apologize. Still, people might not trust your website that is not https, no matter how meaningless the https thingy actually is. Hence I was asking if it could be made to use https...with autistic amounts of cringe, I'm sorry. EDIT: Site now works normally and no workarounds are needed. Edited February 21 by pangoomis
defuser Posted February 23 Posted February 23 (edited) Quote http://sweetlow.orgfree.com/download/usb20_win9x.zip This is a very good, stable EHCI driver. I use it for a long time, there are no complaints (serious). Moreover, it turned out to be useful not only for Windows 98, but also helped to solve the problem of "jumping" or halving the frequency of USB port polling in Windows XP (USBEHCI.SYS) on one of the problematic configurations. My only wish is to improve support for real DOS mode as much as possible. Now, after exit to DOS, the keyboard and mouse connected to the EHCI controller that this driver is installed on in Windows 98 do not work. And in order to continue working (type something on the keyboard), you now need to switch the keyboard to the second USB controller, which is controlled by CSM (only a dummy driver is installed on it). And after exiting DOS (Returning to WINDOWS with the "EXIT" command), the driver works as if nothing had happened. That is, it is not correctly unloaded (It does not transfer control back to the CSM BIOS). And this is the only small (Since there is a working workaround), but still very desirable improvement at the moment. Otherwise, everything works very smoothly (Other options I tried either did not work at all, or worked very crookedly, or required pulling the system floor from Windows ME). And this is the most compact and versatile option that does not require making deep changes to the original Windows 98. Edited February 23 by defuser
SweetLow Posted February 24 Posted February 24 12 hours ago, defuser said: My only wish is to improve support for real DOS mode as much as possible. Now, after exit to DOS, the keyboard and mouse connected to the EHCI controller that this driver is installed on in Windows 98 do not work. There is test version: http://sweetlow.orgfree.com/download/usbehci.zip with BIOS EHCI Hand On, but it does not work on all tested systems. With high probability modern BIOSes just omit this function as NT-like OSes (and even ME) just do not have such thing as exit to real mode. Or some condition should met before transition of ownership for USB controller from OS to BIOS but there is nothing in standard about this. 1
defuser Posted February 25 Posted February 25 (edited) Result: http://sweetlow.orgfree.com/download/usb20_win9x.zip - from cold start - it works fine - after exiting to DOS - it doesn't work - after returning to WINDOWS (with the EXIT command) - it works fine http://sweetlow.orgfree.com/download/usbehci.zip - from cold start - it works fine - after exiting to DOS - it doesn't work - after returning to WINDOWS (with the EXIT command) - does not work But there is good news. I found a workaround to enable the mouse (The keyboard is connected to the second port managed by CSM and it works correctly everywhere and always). And so, after the first cold boot in DOS, I saved PCI registers for the USB controller on which the mouse is installed (USB1_GOOD.TXT): Quote Type:PCI Seg 00 Bus 00 Dev 1A Fun 00 Offset:0000 Width:01 86 80 2D 8C 06 00 90 02 04 20 03 0C 00 00 00 00 00 30 40 F7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 34 17 EA 11 00 00 00 00 50 00 00 00 00 00 00 00 0A 01 00 00 00 00 00 00 0D 15 0F 1D 00 00 00 00 00 00 00 00 01 58 C2 C9 00 00 00 00 0A 98 A0 20 00 00 00 00 20 20 FF 07 00 00 00 00 01 00 01 00 05 20 0A C0 00 00 DD 3F 30 0F 00 00 4F 01 00 00 8C 40 00 00 00 00 80 00 11 88 0C 93 70 0D 00 24 01 04 02 00 00 00 00 00 00 00 00 00 13 00 06 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 AA FF 00 00 00 DD DF 27 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF 3C 5E 7F CB 00 00 00 00 88 85 80 00 B1 0F 06 08 08 17 1A 20 -NEXT- And then, booted into WINDOWS. Exit to DOS. The mouse immediately went out (Stopped working). Then I ran RU.EXE and I applied all these data (Which are given above) and the mouse immediately lit up (Earned). This means that the mouse and keyboard just need to be initialized automatically after exiting to DOS via DOSSTART.BAT. And the problem will be completely solved. Content "USB1_BAD.TXT": Quote Type:PCI Seg 00 Bus 00 Dev 1A Fun 00 Offset:0000 Width:01 86 80 2D 8C 06 00 90 02 04 20 03 0C 00 00 00 00 00 30 40 F7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 34 17 EA 11 00 00 00 00 50 00 00 00 00 00 00 00 0A 01 00 00 00 00 00 00 DB 05 D6 1F 00 00 00 00 00 00 00 00 01 58 C2 C9 00 00 00 00 0A 98 A0 20 00 00 00 00 20 20 FF 07 00 00 00 00 01 00 00 01 00 20 04 00 00 00 DF 3F 30 0F 00 00 4F 01 00 00 8C 40 00 00 00 00 80 00 11 88 0C 93 70 0D 00 24 01 04 02 00 00 00 00 00 00 00 00 00 13 00 06 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 AA FF 00 00 00 DD DF 27 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF 3C 5E 7F CB 00 00 00 00 88 85 80 00 B1 0F 06 08 08 17 1A 20 -NEXT- By the way, when the controller is running, these digits "0D 15 0F 1D" are constantly changing. And when the controller does not work, they freeze and stand still (DB 05 D6 1F). After applying data from "USB1_GOOD.TXT" these numbers come to life again and start moving. Mouse working! Edited February 25 by defuser
SweetLow Posted February 25 Posted February 25 (edited) 1 hour ago, defuser said: I ran RU.EXE and I applied all these data (Which are given above) and the mouse immediately lit up (Earned). This means that the mouse and keyboard just need to be initialized automatically after exiting to DOS via DOSSTART.BAT. And the problem will be completely solved. 1. I have some planned test - try to do BIOS EHCI Hand On not in driver, but under DOS - really like you did (and I already have code for BIOS EHCI Hand Off under DOS). But it is not a high priority. 2. BIOS HAS TO do the things you did with controller manually exactly when BIOS EHCI Hand On takes place - but it does NOT. Edited February 25 by SweetLow
SweetLow Posted February 25 Posted February 25 (edited) 1 hour ago, defuser said: I found a workaround to enable the mouse P.S. And try to check some USB Storage - will it work too? Edited February 25 by SweetLow
defuser Posted February 25 Posted February 25 2 hours ago, SweetLow said: P.S. And try to check some USB Storage - will it work too? Yes, all three are working now: keyboard, mouse and flash drive.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now