LoneCrusader

No problem. Yes, the VIA issue is a real PITA. If only the driver stack files had different names, then fixing the .INF's as discussed would cure it.

I would be interested to apply the fix/patch for 95B, to support USB drives please. Peter -Any luck getting past the protection error? Microsoft made one heck of a mess with the USB updates for Windows 95. As long as you know what to do beforehand, then you should be OK. If not, it can be extremely confusing. There are two official USB Support packages. The first of which (USBSUPP.EXE) had two versions issued (first version was bugged and should NOT be used). Then USBUPD2.EXE was issued to correct bugs in the first package. Finally there were several "HotFix" files issued that further updated the drivers. Then, on top of that, there are semi-complete unofficial packages to support USB Flash Drives (which may be superseded in the near future.) I have been planning to merge all of these updates into a single package to simplify things. If you're willing to wait a couple of days, I will try to get it assembled. If you want to go ahead and wade through the mess, I will walk you through it.

Here you go LOGO98SE.ZIP - 105.0 Kb

I'm not aware of any bootable Windows 95 CD's, for PC's without Windows or otherwise. But it's simple enough to create your own bootable CD. Anyway.. If you are using a "For PC's Without Windows" CD then it must be 95/95A rather than 95B/95C because the B/C versions only exist as OEM CDROMs. I have seen some errors reported using FIX95CPU with 95/95A. I did not have a copy of 95/95A to test with when I created FIX95CPU, so the results on those earlier versions may not be ideal or exactly the same as 95B/95C.

@PROBLEMCHYLD You do know that the startup & shutdown logos will lose the animation in in the bottom bar if edited with Paint or a similar program? You need a utility to restore the animation after the edits, such as XrX AddBar. I can fix them for you if you've not already done this...

So I used GIMP Portable, a free app available here - http://portableapps.com/apps/graphics_pictures/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.

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?

No, not quite. Windows 95 CDROM's are not bootable. My slipstreaming instructions were directed at those who wish to modify their installation source. If you're just going to copy and re-modify it each time you install, why not just use FIX95CPU as-is?

Cold or Warm boots should not matter in this case. Drive configurations might be an issue at some point, but I don't think it has anything to do with the current problem. Couple of other questions for the record that may make it easier to figure out what is going on... - Did you have any of the USB Support updates previously installed on this Win95 HDD? (MAJOR changes to several core system files, so we need to know whether we're working with pre-USB 95B or post-USB 95B.) - What are the specs of your motherboard & integrated hardware on it? Brand, Model, etc.

What is the "Explorer" message and Blue Screen you're getting? Strange. The only failure listed is on an attempt to load VSHARE. However, VSHARE was reported successfully loaded earlier in the file. I believe this has gone out of my realm of experience. Maybe rloew will have some suggestions. Don't give up yet.

If you want to use the 2GB of RAM, you will need to get the full version of the RAM patch. That's really the only option for using that much RAM... As you see, it is working and allowing you to get to Safe Mode. Very odd that you cannot boot in Normal Mode though... I'd say that there's a possibility there are still some issues caused by old drivers. Go into the BIOS on your motherboard and disable any Onboard Devices that you can, such as Audio, LAN, USB, Modem, etc, and see if it will allow you to boot into Normal Mode without errors. If so, then we can work on reenabling them one at a time and finding drivers to try and straighten it out. I'm not sure what else to try, other than while in Safe Mode, go ahead and install DUN14-95 and see if the BOOTLOG.TXT for booting in Normal Mode still reports errors (if so post it here). Other suggestions, anyone?

Not necessarily, YMMV here. I've been using SOYO boards since 2005 (including that particular model) and never had any capacitor issues.

Sounds good. I don't think I'm up to that search tonight anyhow... 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.

Aha! Only bad thing is now I'm going to have to dig around through all those files and see if there are any versions later than 5.0.2195.5605 but before 5.0.2195.6891.

Always put your health first. You will get to it someday Do you mean USBHUB20.SYS?

Hmmm... This is HIGHLY speculative. No idea whether this would be the case or not! Any chance that such a device would be treated as a "Composite Device?" If so, there may or may not be differences in behavior now that changes have been made to NUSB, etc. Under Win98SE and Win2K, composite devices use USBHUB.SYS (or USBHUB20.SYS for USB2). Under WinME and WinXP, composite devices use USBCCGP.SYS. Now that the Windows ME USB1.1 stack and ME-style USB.INF (with use of USBCCGP.SYS) has been implemented, such devices MAY not depend on USBHUB20.SYS anymore. So the bug may not even exist at all so long as one has a complete collection of the latest unofficial USB updates. Someone who knows more about this than me please chime in...

I tend to prefer using the MS stack if the older versions don't have the bugs with VIA chipsets, but I agree the other option should be tested and considered as well. I have the same problem you do regarding UHCI/OHCI so I can't help with testing the second option. All of my hardware is Intel based with UHCI USB 1.1 controllers. (And man, has it been a pain for a project currently in development that I've been involved in. )

I found USBHUB20.SYS v.5.0.2195.5605 inside this package (issued for Q319973). There may be others, but I'll have to look through all of the many, many packages I downloaded again. Maybe someone can test that version and see if it has the same bugs as the later one... My next question was going to be whether or not the VIA USB2 stack works for all other chipsets, and if so, suggest using it instead. Similar to your suggestion.

Since the older machine still works, you might try one last thing. Put the HDD back in the older machine. Boot into Safe Mode. Go into the Device Manager and remove anything and everything that is listed there. Then Shut Down and try the HDD in the new machine again. If any older drivers are causing problems, this should correct it. If it doesn't, then you should be able to reconnect the HDD to the older machine again and let it redetect devices.

You said you moved the HDD from another computer... I'm assuming you have data/programs on it that you wished to save? If not, I recommend a clean installation of 95B, just in case there are any old settings/drivers/files left over from the previous machine that may be causing errors.

Good point about add-in cards. I wasn't thinking. Driver files interdependent on one another may not be able to interact with each other if renamed. Often they have internal references to one another. Theoretically one might be able to Hex them all and change the names internally and externally, but that would also have to be proven in practice. Another angle: (dencorso please comment on this, you seem to be the most informed member about this) Do we know 100% for sure that ALL versions of the MS USBHUB20.SYS cause errors/do not work with VIA controllers? Or is it just the version used by NUSB? Earlier versions of the MS USBHUB20.SYS driver exist (I tracked them down trying (unsuccessfully) to find the oldest possible versions of a USB2 stack to load on Win95). I can provide a link if someone can test.

No problem. Let us know if the patch works for you!

Renaming the VIA driver files may result in them not being able to properly interact with one another. I can't say that for certain, but I have a feeling it isn't a good idea. I started to suggest having them install to a different folder than the MS files, say SYSTEM32\DRIVERS\VIAUSB2 instead of just \DRIVERS, but that may break their ability to interact with other files in the \DRIVERS directory. I believe WDMCHECK will report missing functions from files that are not in the same folder as the file being checked... I would think that moving the VIA data to a separate INF file would be sufficient. I don't know of any situations where two different branded USB2 controllers would exist in the same system, but maybe I'm wrong...

You will need to use WinZip, WinRar, 7-Zip, etc, to extract the file from inside the HotFix on another computer. MS HotFixes are usually "Self-Extracting Executables" and can be opened with archiving programs.

VCACHE.VXD is merged into VMM32.VXD along with several other VXD's during the second phase of SETUP, so you won't find the file after that. All MS HotFixes require Windows to run. Pretty useless when you can't boot to Windows to begin with. That's why I created FIX95CPU to install the updated CPU fixes. In order to update your VCACHE.VXD, you will need to manually extract VCACHE.OSR (it contains two VCACHE files, one for 95/95A and one for 95B/95C) from the HotFix file I linked, rename it to VCACHE.VXD, and manually place it in your WINDOWS\SYSTEM\VMM32 folder. The Boot Image of an .ISO is not visible without tools for viewing/extracting/editing etc. FIX95CPU.ISO contains a boot image of the FIX95CPU floppy, with DUN14-95.EXE added to the "normal" part of the ISO for convenience. I wish you success in your endeavor, but in my personal experience, if you want to use more than 512MB of RAM, you will need RLoew's RAM Limitation Patch. Several users here report success using up to ~1.5GB with the tweaks you have been experimenting with, but those tweaks never worked on any of my systems. (Also, many of those users are using 98SE, which may handle the larger RAM amounts better than standard 95B/C can.) The patch has a DEMO version that runs for 10 minutes. You might try downloading it and see if it cures your problem.