[TmEE]

PROBLEMCHYLD, on 22 November 2012 - 07:10 PM, said:

The Windows start menu changes to the default by design because people wanted the original icons/start banner. This is not a bug. You will need to check the box Windows Millennium Edition/Windows 2000 Theme for the updated icons, only after you have installed Main Updates. Do USBHUB20.SYS 5.0.2195.6891 work with your VIA chipset? Thank you very much for helping me get SP3.x stable I think 3.10 will be for many users to come.

Aha, I did not know main updates revert the graphics, that is good to know ^^

I will see what file there is, I certainly have had no problems so far.

[Drugwash]

LoneCrusader, on 23 November 2012 - 02:15 AM, said:

dencorso, on 23 November 2012 - 02:09 AM, said:

I don't think so. There sure is a usbhub.sys 5.00.2195.6689 (USB 1.x) but I don't think that version of usbhub20.sys was ever released.

I thought the version number didn't sound right, but USBHUB.SYS should be 4.90.3002 on a 98SE system with the current updates, unless some Win2K USB1 stack files have been added...

EDIT:
I remember now, some discussion was made earlier about using the Win2K USB1.1 stack. Not a matter of universal agreement as I recall.

It's usbhub.sys alright, not 2.0. Can't remember when and how it got installed - either through a NUSB update, or by my manual fiddling with driver files. It's been a while though since I let this system settle, as the other one decided to die on me (HDD developed 4000+ bad sectors) and I need it for my programming hobby. However, in the past I used to replace all kinds of system files from whatever OS was needed, when some newer application cried for missing APIs. My Windows folder is currently 1.72GB, complete with .NET 1.0, 1.1 and 2.0.

[jaclaz]

Very possibly I am wrong , but checking WHY exactly a given new version was posted as hotfix might give some hints and possibly let us decide that after all a previous version would be preferrable (or not):
http://blogs.msdn.co...ws-version.aspx

jaclaz

[PROBLEMCHYLD]

dencorso, on 23 November 2012 - 01:42 AM, said:

I have to report that, despite my best efforts, I've been utterly unable to elicit a BSOD from Usbhub20.sys v. 5.0.2195.5605.
Rest assured that the hub I used is not seen as a Composite Device, but simpliy as a "Generic USB Hub" (USB 2.0, High Speed) from Alcor Micro (VID=0x058F; PID=0x6254).

That's great Now that we know its possible to use the Microsoft version with VIA devices, we should look into maybe patching the latest version instead of backtracking. If it is not possible to patch the latest version, I will downgrade the file, but continue to use the newer version on my own system.

dencorso, on 23 November 2012 - 02:09 AM, said:

I don't think so. There sure is a usbhub.sys 5.00.2195.6689 (USB 1.x) but I don't think that version of usbhub20.sys was ever released.

The SP installs version USBHUB.SYS 5.0.2195.7006

jaclaz, on 23 November 2012 - 08:02 AM, said:

Very possibly I am wrong , but checking WHY exactly a given new version was posted as hotfix might give some hints and possibly let us decide that after all a previous version would be preferrable (or not):
http://blogs.msdn.co...ws-version.aspx

jaclaz

Thanks, but all those hotfixes are already included in SP using the latest compatible files There are more Windows 2000 and XP (combined) in SP than there are Win98. Way to go MSFN. I even thought about changing the name to Unofficial Windows 98 Second Edition Hybrid Pack becuase it has files from almost every operating system and yes, they WORK!

This post has been edited by PROBLEMCHYLD: 23 November 2012 - 09:22 AM

[dencorso]

Bear in mind that the issue with USBHUB20.SYS is *very* specific: it requires one to actually remove a USB 2.0 hub to manifest the BSOD, and then, if one hits <Enter> two or three times (IIRR), one does get back to the desktop and can restart all right, or even continue to work (although the OS is not necessarily safe to be used after recovering from a BSOD). The Win 9x/ME and 2k USB stack is peculiar, because it's bifurcated: even if the physical connectors/ports are the same (which they can perfectly be), the OS treats USB 1.x and USB 2.0 communications as two separate things (while Win XP and higher adopt a unified USB view). So one must have a hub, it must be a 2.0 hub and it must have actually been detected as a 2.0 hub on that particular insertion (sometimes USB 2.0 devices are not detected as 2.0, for some random reason). These three factors one can check using USBVIEW. At this point one inserts at least one USB 2.0 mass storage device, lets the system read it, then safely remove the device, letting the hub stay. The hub itself is not a mass storage device, so it cannot be stopped or ejected, before removal. So after letting the hub remain for at least 20 seconds after safe removal of the mass storage device, one may grab the hub and remove it. Then the BSOD happens. If, instead of removing just the mass storage device, then waiting, then removing the hub one removes the hub with the mass storage device still connected to it, the BSOD also happens. But if one never removes the hub, one'll never see the BSOD. Sorry, this description became long-winded, but I want to make it clear how to test for this BSOD. And, of course, if one doesn't have a VIA USB 2.0 controller, then there's nothing to test.

[TmEE]

I experienced the BSOD too if I hooked my USB 2.0 hub and then removed it after I had used some flash sticks (that worked perfectly). I only needed one button press to get out of it and then refresh desktop as everything was black.
This happened on a VIA VT6212L USB 2.0 controller.

[PROBLEMCHYLD]

TmEE, on 24 November 2012 - 04:43 PM, said:

I experienced the BSOD too if I hooked my USB 2.0 hub and then removed it after I had used some flash sticks (that worked perfectly). I only needed one button press to get out of it and then refresh desktop as everything was black.
This happened on a VIA VT6212L USB 2.0 controller.

Thanks, can you try this version now? USBHUB20.SYS 5.0.2195.5605

[TmEE]

I just tested this file and it still gave the BSOD.

[PROBLEMCHYLD]

This is what we have so far

TmEE - VIA VT6212L
Drivers not working - USBHUB20.SYS 5.0.2195.5605, USBHUB20.SYS 5.0.2195.6891

Drugwash - VIA VT6202
Drivers working - USBHUB20.SYS 5.0.2195.6891

dencorso - Generic USB Hub
Drivers working - USBHUB20.SYS 5.0.2195.5605
Drivers not working - USBHUB20.SYS 5.0.2195.6891

I don't think its fair to downgrade the file to a lower version and deprive others of the newest and stable code, especially when they have not experience any problems. I also think its unfair to inconvenience users who are not able to benefit from the lastest version. That would mean everytime a new update is release, users with VIA chipsets will have to manually replace the file, which will become an annoyance. I'm hoping we can find a universal solution that suits everyone needs. As I said earlier and other may feel the same way, I prefer not to use VIA anything, if I don't have anything VIA related

[bphlpt]

Hey PROBLEMCHYLD,

As requested, here is the modified LOGO.

http://www.mediafire...crm8gkq04ylr8ab

or

http://www.mediafire...m5r46960u2fd39h

Cheers and Regards

This post has been edited by bphlpt: 25 November 2012 - 10:28 PM

[MiKl]

On saturday SeaMonkey crashed with an error message relating to : ddeml.dll
I have version 4.10.1998 dated 5.5.1999 running in my Win98SE but there is a version from 2001 in my XP !
So far I did not had the time to test it but I thought I let you know because it seem to be not in your ServicePack, PC. Maybe with a good reason though ....

Seem to cause BOSD ... dammit, Janet

This post has been edited by MiKl: 26 November 2012 - 12:26 PM

[North of Watford]

Before we all conclude that the VIA USB problem has been resolved, I may have a problem.

This is not yet definitive, proven or reproducible, I need to do a lot more work on it for reasons that will become obvious. I recently updated one of my Win98 boxes (the one with a VIA chipset for everything) using SP3.10 . I was interrupted in the course of the job, and am not certain that I did it correctly.

I then used the box without any difficulty until yesterday when I plugged in a USB stick for the first time. Immediate BSOD! Cleared with one click of the space bar, and continued to check the stick for contents, including opening a couple of files. Then I went to remove the stick using the remove media button in the tray. Another immediate BSOD that flickered on pressing the space bar, but looped back to the same location. Resolved by a power off.

I am pretty sure that I hadn't done something right earlier. Request: is there a consolidated list of all the files and version numbers that should be on a correctly updated box; files that have been installed by the updating process?

As soon as I find out what was the cause, I'll be right back to 'fess up, so that others can avoid the trap.

Jeff

[PROBLEMCHYLD]

North of Watford, on 26 November 2012 - 04:39 PM, said:

Before we all conclude that the VIA USB problem has been resolved, I may have a problem.

This is not yet definitive, proven or reproducible, I need to do a lot more work on it for reasons that will become obvious. I recently updated one of my Win98 boxes (the one with a VIA chipset for everything) using SP3.10 . I was interrupted in the course of the job, and am not certain that I did it correctly.

I then used the box without any difficulty until yesterday when I plugged in a USB stick for the first time. Immediate BSOD! Cleared with one click of the space bar, and continued to check the stick for contents, including opening a couple of files. Then I went to remove the stick using the remove media button in the tray. Another immediate BSOD that flickered on pressing the space bar, but looped back to the same location. Resolved by a power off.

I am pretty sure that I hadn't done something right earlier. Request: is there a consolidated list of all the files and version numbers that should be on a correctly updated box; files that have been installed by the updating process?

As soon as I find out what was the cause, I'll be right back to 'fess up, so that others can avoid the trap.

Jeff

Thank you for testing. We are working on a universal solution right now. Thank you for your patience, You can use USBHUB20.SYS 4.90.3000.11 for the time being.

[PROBLEMCHYLD]

MiKl, on 26 November 2012 - 06:33 AM, said:

On saturday SeaMonkey crashed with an error message relating to : ddeml.dll
I have version 4.10.1998 dated 5.5.1999 running in my Win98SE but there is a version from 2001 in my XP !
So far I did not had the time to test it but I thought I let you know because it seem to be not in your ServicePack, PC. Maybe with a good reason though ....

Seem to cause BOSD ... dammit, Janet

I really don't understand your post The SP doesn't install any DDEML.DLL versions. I'm really not sure what your problem is

Here's what SP 3.12 will have so far

Added MANGAL.TTF Microsoft VOLT 1.2
Added TEMPSITC.TTF Plus!98 CD
Added Original start up and shut down logos with [Second Edition]

[LoneCrusader]

bphlpt, on 25 November 2012 - 10:24 PM, said:

Hey PROBLEMCHYLD,

As requested, here is the modified LOGO.

http://www.mediafire...crm8gkq04ylr8ab

or

http://www.mediafire...m5r46960u2fd39h

Cheers and Regards

Nice job with these logos.
(I assume there is a Startup one as well as the Shut Down one?)

I have tried and tried to create similar ones myself, but I never could seem to get the right Font, letter height/spacing, etc etc.

Are you accepting other logo requests by any chance?

[bphlpt]

LOL Thanks, but I'm not that good. I just took the two LOGOS that PROBLEMCHYLD already did over a year ago - LOGOS - He asked me:

PROBLEMCHYLD, on 25 November 2012 - 01:55 PM, said:

I need you to take the text Windows is shutting down. from LOGO2.BMP and add it to LOGO1.BMP. Leave all colors/text format/file size the same.

So I used GIMP Portable, a free app available here - http://portableapps....s/gimp_portable - and did a cut-and-paste of the text Windows is shutting down. I exported the new image, GIMP's version of "save as", to LOGO3.BMP, and that was it. So there was no choosing the Font or letter height/spacing or anything. The background was such that the paste didn't show. (I'm lazy, so I took the easiest way out. ) I appreciate the kind words though. If you have a similar simple request I'd be glad to give it a shot, but no promises. I'm no larryb123456 after all. Send me a PM if you like, to not clutter up PROBLEMCHYLD's thread.

This post has been edited by bphlpt: 28 November 2012 - 02:42 AM

[LoneCrusader]

bphlpt, on 28 November 2012 - 02:37 AM, said:

LOL Thanks, but I'm not that good. I just took the two LOGOS that PROBLEMCHYLD already did over a year ago - LOGOS - He asked me:

PROBLEMCHYLD, on 25 November 2012 - 01:55 PM, said:

I need you to take the text Windows is shutting down. from LOGO2.BMP and add it to LOGO1.BMP. Leave all colors/text format/file size the same.

So I used GIMP Portable, a free app available here - http://portableapps....s/gimp_portable - and did a cut-and-paste of the text Windows is shutting down. I exported the new image, GIMP's version of "save as", to LOGO3.BMP, and that was it. So there was no choosing the Font or letter height/spacing or anything. The background was such that the paste didn't show. (I'm lazy, so I took the easiest way out. ) I appreciate the kind words though. If you have a similar simple request I'd be glad to give it a shot, but no promises. I'm no larryb123456 after all. Send me a PM if you like, to not clutter up PROBLEMCHYLD's thread.

Ah I see.

I was going to request a slight variation in the location of the "Second Edition" text (closer to the "Windows 98" text, similar to how the "Microsoft" text is, but maybe not right against it...) and to have the same "Second Edition" text added to the Windows 98 Plus! logo.

I don't think that can be done with copy and paste though, as it would leave a "rectangle" around the text visible in the background.

[bphlpt]

Try me. Provide all existing LOGOS you can that have the text and don't have the text and I'll see what I can do.

EDIT: I had actually first thought about cutting and pasting the "Second Edition" text from LOGO1.BMP over to LOGO2.BMP until I realized that the bottom strip was more indicative of the shutting down procedure, so your idea might well be possible.

Cheers and Regards

This post has been edited by bphlpt: 28 November 2012 - 08:25 AM

[PROBLEMCHYLD]

@ bphlpt

I actually got that LOGO from MDGx site. I'm sure he would be more than happy to add the shutdown version to his logos pack. A very big thank you for taking the time to do it.

[bphlpt]

He's more than welcome to it. With all he has done for the community it's the least I can give back. Since it's your doing that got me to do it, it's also perfectly fine with me that the submission to him come from you.

Cheers and Regards