LoneCrusader

Yes. I posted that when I was in a hurry I'm glad this subject has come up however, and that you all seem to be finding other solutions besides IntelliPoint. I have been trying unsuccessfully to figure out how to "slipstream" Wheel Mouse support into my 95 project. I tried downversioned 98 files to no avail, and I tried to "rip" what I needed out of IntelliPoint but that doesn't work either. Maybe one of these other approaches could be used.

Thanks Worth noting however that 4.12 will NOT work on 95. It only works in 98 & up. I have IP 4.0 and can upload it somewhere if anyone needs it.

The only way to get a Scroll Wheel working in Windows 95 is to install Microsoft IntelliPoint 4.0. EDIT: Incorrect information struck through. See Post #46.

I use ATi Radeon 8500 128MB's in my Windows 95 boxes. I have an original drivers disc for one from back when 95 was still supported. Later ATi cards may work as well, but it's been a while since I tried experimenting with them. I think I had a 9200 working at one time, but I believe my 9800 XT's had some issues. Note - there will be various errors about missing DLLs, exports, etc etc unless you be sure to install DX8 and several other updates before attempting to install any "newer" drivers. One DLL in particular that installers will complain about is MFC42.DLL. It is contained in the updates or it can be copied from a 98 machine.

Firefox 2.0.0.20 with Java 6 Update 7 and Flash 9.0.289. I have never used KernelEx on any of my real machines. I tried installing it once in a VM and had no text in any menu in Firefox 3. So far I haven't needed anything more than Firefox 2 with the User Agent Switcher installed to do the things I need to do. If you're determined enough you can still force Yahoo to show you the classic version. I don't know for how long, but we can hope. I absolutely despise GMail. I have always hated it, and I will continue to hate it. I can't stand how it combines emails into "conversations" and then you can't get the d@mn things apart again. Edit: Agreed with you about Opera Drugwash, I hate Opera.

Huh? Why? I use Yahoo Mail and I prefer it to Hotmail or Gmail garbage. I don't have any problem accessing it. Of course I refused to allow them to force me to upgrade to their "new" mail. It should work fine at least until they manage to permanently kill the classic version.

Well said jaclaz. I agree. I think USP's should only contain official MS updates in the main install, and if the creator wants to add options for unofficial fixes, special tweaks, and/or program replacements, fine, but they should be strictly optional and not interdependent. My gripe with the 98SE USP is that it makes tweaks that are incompatible with RLoew's RAM Limitation Patch. A test system of mine with both installed was very unstable and did not correctly report the amount of RAM installed. Without the USP, there is no problem. The Windows 95 OSR 2.x USP crashed one of my test systems as well. It seems to be incompatible with my FIX95CPU upgrade which contains only official MS fixes (with the sole exception of RLoew's PTCHCDFS). Agreed. But as you see, not all of us even agree on what is "essential." Many here would deem the USP "essential," whereas I would list it as "to be avoided." I have always found P4-class processors to be extremely fast and reliable, especially when running Windows 9x. Of course I should also point out that all of my P4's are 2.8GHz or faster (except a couple of 2.0 GHz ones I had stockpiled from before I broke the 95 2.1GHz barrier). IMHO, you have not really experienced Windows 9x until you have run it on P4-equivalent hardware. You click and things are done. It's a situation where the hardware is finally fast enough to make the OS fun to use. They make the hardware faster, and Microsoft makes the software slower. It's an endless cycle. I imagine that machines now supposedly designed for Windows 7 would be excellent for running XP. I am most certainly no expert on malware. In all of my computing days, I have only contracted a virus on my home machine once. I do not use Antivirus software, because IMHO, it operates in the same manner as a virus - it slows down my machine and is a real pain to get rid of once installed. My policy is somewhat similar to the one you stated above - I use common sense and don't go to the wrong places or click on the wrong things. I would surmise that the XP problem I described came from something that was embedded into the websites that were displayed as results by Google Image search.

I have seen several people make this request, and I understand where you are coming from. The problem with making such a thread is that not everyone wants the same updates made to their system, not everyone wants the same modifications made, etc etc etc. For example - I regard NUSB as an integral part of any Windows 98 setup. However I do not use and do not recommend the Unofficial Service Pack. Many people love Tihiy's Revolutions Pack, and I greatly admire his ability and his dedication, but I like my Windows 98 GUI just like it is by default. The last thing I want to do to it is disgrace it with some XP lego-look. In fact, if I had to choose between Windows Vista and Windows 7, I would take Vista for one reason - it still has the classic Start menu. And the list goes on. These updates are chosen by personal preference, and some are incompatible with each other or require special tweaking to work together. Simple - you buy RLoew's RAM Lmitation Patch and install it. Problem solved. No trial-and-error. No editing INI files or any such rubbish. No Tweaking. No looking back. As for the CPU's, I am aware of no issues with modern CPU's other than the fact that Windows 9x cannot use multiple processor cores. It can be run on those processors, but will only use one core. Whats more important is drivers for current motherboards. Lack of driver support for newer hardware is IMO the worst hurdle facing Windows 9x at this point. However, 9x drivers exist for P4-class motherboards and some of the early 9xx series Intel chipset boards. While I was at college, I got a virus on the XP machines there TWICE by simply searching for pictures on Google. Nothing "out of the way" either, I was trying to find a picture of a car to show a friend. And these machines have SP3, Virus Scanners, and DeepFreeze. DeepFreeze cured it with a reboot, but the fact remains - a simple Google search produced an infected machine. It's not easy, and I wish I had more time and had more knowledge. If I ever win the lottery maybe I'll hire someone to do nothing except work on Windows 9x issues.

Oh I have plenty of issues that matter to me other than my choice of operating systems. This is not necessarily the forum for their discussion. Try translating or searching for the phrase under my avatar, and you may have some idea. I would use Linux before I would use an NT-Kernel based Windows. And when/if the day comes that my Windows 98 won't do what I need it to do, then Linux is where I will go. Microsoft lost my "support" for good when they abandoned 9x, and they will never get it back.

As others have stated, the majority of your problem comes from Dial-Up, not from Windows 98. I spent over 6 years on it myself, so I know how it is. Also, if you are serious about running Windows 9x systems these days, IMHO you need to max out your hardware. 9x drivers exist for Pentium 4 class hardware, and with RLoew's patches you can correct RAM, HDD, and SATA issues. I use Windows 98 on a daily basis, for everything I need to do. Now that means I have to accept that some things will not work or not work 100% properly. But that doesn't matter to me, I accept it and deal with it. I keep a copy of Windows XP for the few games I have that require it, and for handling >4GB files - but that is ALL I use it for. And I'll be d@mned if I EVER use Windows 7. At least Vista still has the Classic Start Menu. It does take a lot of dedication however. I'll admit that it is frustrating sometimes. But I'm an idealist, I'm dedicated. If something doesn't work with Windows 98, then I will avoid using it. Until only a couple of years ago, I refused to purchase ANYTHING whatsoever that connected by USB, simply because it would not work with Windows 95. To this day the only USB hardware I own are flash drives and USB-to-IDE adapters for hard drives. I don't compromise my positions or my principles for convenience - and I'm used to being on the side of the minority.

I suspect adding a CAB would be tricky. I've never tried it, just placed added files into the original CABs, trying to follow any logical "patterns" present, for example placing DLL files in a CAB with other DLLs, INF's with INF's etc.

I've never seen this occur... this behavior is not present in VMware Workstation or VirtualPC. Of course I don't have a similar USB-Floppy drive setup though. Maybe VirtualBox is mapping the entire USB device to 95 instead of the floppy by itself, and 95 is trying to compensate... Which version of 95 are you running? My tests were all performed with 95 B/C setups, RLoew did the testing on 95/95A setups. He did identify a bug wherein the floppy drive was sometimes not recognized properly with these earlier versions. I scripted FIX95CPU to not update the file that causes this in 95\95A... Maybe RLoew can elaborate a bit on the floppy error he encountered. Windows 95's USB support is badly lacking... (although I am beginning to believe part of this was by design or due to outright laziness, the INF file has an unresolved bug actually LABELED in it! ). Unless VirtualBox is able to "translate" the USB floppy into a standard floppy there are bound to be problems.

The slipstreaming tools are actually not listed there yet. I know RLoew has been very busy lately with updating some of his other tools and creating an initial release of advanced CD/DVD/BD tools, so I don't know if he plans to add them right now or not. He may address this here, or you may want to send him an email.

I stand corrected. However some of your tools would still be required. Yep. I used this method for "slipstreaming" my Windows 95 processor updates to bypass the IOS and NDIS "Windows Protection Errors" up until I purchased the tools to update the CABs themselves. BTW, with these tools you can also add new files and new functionality if you know what you're doing and have a LOT of patience. I have slipstreamed 80+ HotFixes along with NUSB and USB 2.0 support into a standard 98SE installation.

Replacing files inside the CABs is rather complicated. It's not as simple as just rebuilding one CAB with a new file inside. The Windows 9x CABs are all "linked" together and files can be split across multiple CABs. Any given CAB may contain a whole file, the beginning of a file, the middle of a file, or the end of a file. Some do not even contain a whole file at all, just part of one. It's like splitting up a very large file with WinRAR or a similar program. You cannot just edit one "piece" of the whole. I have purchased a set of tools from RLoew that allows slipstreaming, but without them it would be a nightmare to attempt. If all you need to do is add one or even a small handful of files, the best course will be to simply place the updated files in the same folder as the CABs when you install Windows 9x. You can do this by burning a CD with the new files added into the \WIN9x folder, or you can copy the install files and the updated files to a folder on the hard drive to install them. Windows 9x Setup will automatically use any files outside the CABs instead of the older version inside the CABs.

No problem, you're welcome

The Batch98 tool can be used for ME as well. Everything is essentially the same, just some of the install options will be different and/or may have slightly different names. The most important thing when using MSBATCH is the product type of your copy of Windows. It will affect how well or your script works or whether it works at all. OEM versions can be a PITA. This is my MSBATCH.INF for Windows ME (Full Retail Version): ; MSBATCH.INF FOR WINDOWS MILLENNIUM EDITION ; ; Copyright (c) 1995-1998 Microsoft Corporation. ; All rights reserved. ; [BatchSetup] Version=3.0 (32-bit) SaveDate=01/17/10 [Version] Signature = "$CHICAGO$" AdvancedINF=2.5 LayoutFile=layout.inf [Setup] Express=0 InstallDir="C:\WINDOWS" InstallType=3 OptionalComponents=1 ShowEula=0 ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" EBD=0 Uninstall=0 TimeZone="Eastern" [System] Locale=L0409 SelectedKeyboard=KEYBOARD_00000409 [NameAndOrg] Name="Your Name" Display=0 [Network] ComputerName=YourComputerName Description=YourComputerDescription Clients=VREDIR Protocols=NWLINK, MSTCP Security=SHARE [NWLINK] Frame_Type=4 [MSTCP] DHCP=1 DNS=0 WINS=D [VREDIR] ValidatedLogon=0 [OptionalComponents] "Accessibility"=0 "Accessibility Options"=0 "Accessibility Tools"=0 "Accessories"=1 "Briefcase"=0 "Calculator"=1 "Desktop Wallpaper"=1 "Document Templates"=1 "Games"=1 "Imaging"=1 "Mouse Pointers"=1 "Paint"=1 "Quick View"=1 "Screen Savers"=1 "Additional Screen Savers"=1 "Flying Windows"=1 "OpenGL Screen Savers"=1 "Windows Scripting Host"=1 "WordPad"=1 "Communications"=1 "Dial-Up Networking"=1 "Dial-Up Server"=0 "Direct Cable Connection"=1 "Hyper Terminal"=0 "Microsoft Chat 2.5"=0 "NetMeeting"=0 "Phone Dialer"=0 "Virtual Private Networking"=1 "Desktop Themes"=1 "Baseball"=1 "Dangerous Creatures"=1 "Desktop Themes Support"=1 "Inside your Computer"=1 "Jungle"=1 "Leonardo da Vinci"=1 "More Windows"=1 "Mystery"=1 "Nature"=1 "Science"=1 "Space"=1 "Sports"=1 "The 60's USA"=1 "The Golden Era"=1 "Travel"=1 "Underwater"=1 "Windows 98"=1 "Internet Tools"=0 "Microsoft FrontPage Express"=0 "Microsoft VRML 2.0 Viewer"=0 "Microsoft Wallet"=0 "Personal Web Server"=0 "Real Audio Player 4.0"=1 "Web Publishing Wizard"=0 "Web-Based Enterprise Mgmt"=0 "Multilanguage Support"=0 "Baltic"=0 "Central European"=0 "Cyrillic"=0 "Greek"=0 "Turkish"=0 "Multimedia"=1 "Audio Compression"=1 "CD Player"=1 "Macromedia Shockwave Director"=1 "Macromedia Shockwave Flash"=1 "Media Player"=1 "Microsoft NetShow Player 2.0"=1 "Multimedia Sound Schemes"=1 "Sample Sounds"=1 "Sound Recorder"=1 "Video Compression"=1 "Volume Control"=1 "Online Services"=0 "America Online"=0 "AT&T WorldNet Service"=0 "CompuServe"=0 "Prodigy Internet"=0 "The Microsoft Network"=0 "MSN Messenger Service"=0 "System Tools"=1 "Backup"=1 "Character Map"=1 "Clipboard Viewer"=1 "Disk compression tools"=1 "Drive Converter (FAT32)"=1 "Group Policies"=0 "Net Watcher"=1 "System Monitor"=1 "System Resource Meter"=1 "Web TV for Windows"=0 "Broadcast Data Services" "WaveTop Data Broadcasting"=0 "WebTV for Windows"=0 "Internet Connection Sharing"=0 "Dial-Up ATM Support"=0 "Outlook Express"=1 "Address Book"=1 "Macromedia Shockwave"=1 "Classic Games"=1 "Internet Games"=1 "Plus! Games"=1 "Compressed Folders"=1 "EarthLink"=0 "Windows Millennium"=1 "Universal Plug and Play"=1

I don't know what world you live in, but some people in this one have to work for a living. And RLoew does that by programming. You should respect his ability and appreciate that he spends ANY of his time on the "antiquated" systems that we love. Everything in this world is not free, and it never will be.

Thanks for taking a look at my findings. There is a small bug however, the USB.INF I posted didn't have sections for [sourceDisksNames] and [sourceDisksFiles] and still has the "LayoutFile=Layout.inf, Layout1.inf, Layout2.inf" line inside it. So, on installation it tries to get the files it needs from the CABs instead of from NUSB. If your CAB files are anywhere besides the standard OPTIONS\CABS folder it will stop and ask for the location of HOTPLUG.DLL (not in the original CABs, so you have to manually redirect it to where NUSB has extracted its files), and then it will try to replace the ME files with 98 ones (it prompts you to keep the newer one though). It has no trouble finding USBCCGP.SYS, which is not in the CABs either though I believe the LayoutFile= line needs to be removed, and the [sourceDisksNames] and [sourceDisksFiles] sections added, using the same method as USB2.INF. I didn't make those changes myself because I am not familiar with creating "HotFix" type packages. EDIT: I tried making the changes I listed on a test installation, and the behavior didn't change. I hope someone with a bit more knowledge on this will take a look at it. I believe this is only an issue if Windows 98SE was installed from somewhere other than \OPTIONS\CABS. Anyone who encounters this will need to redirect the Driver wizard to %WinDir%\OPTIONS\CABS where NUSB extracts all of the new files. After that, everything is fine.

What??? $11 dollars is expensive? IMHO, the question here is, do you want this machine to work and be stable, or not? How important is it? If it is important, bite the bullet and fix it right. I seriously doubt it will ever be in a usable state with this cobbled-up mess.

That isn't required. I run several P4 HT Windows 9x Machines (Including Windows 95 machines) with HyperThreading turned on. Windows 9x just ignores it.

I agree with you that the updates should be transparent, I didn't intend for anyone to grab the USB20DRV package and use it in this situation. I listed the thread as relevant because it had some further information not in the "Composite Device" thread. This was meant to be strictly an addition to NUSB. As I stated above, 98SE and Win2K do not have an equivalent of USBCCGP.SYS. They use USBHUB.SYS or USBHUB20.SYS for composite devices. What I have done is based strictly on RetroOS's discovery (and the fact that he was using ME files enabled him to do it.) It works perfectly here on a VM, but I don't have a bunch of USB devices to test it with. I was (and still am) a 95-lover for many years and as such had an extreme dislike for USB devices. Even now I only have flash drives. Edit: Added warnings to the previous post.

Did you try to install USB20DRV directly on top of NUSB 3.3? USB20DRV has some bugs (sorry MDGx ) USB20DRV downgrades USBHUB20.SYS, which should only be done on boards with VIA Chipsets. This should be a stand-alone installer for that one file. The way USB20DRV handles WDMSTUB.SYS doesn't work either, it should only be loaded by USBSTOR.INF as described in that thread by dencorso, not loaded with the USB2.INF & drivers. Also, did you remove ALL USB devices from the Device Manager before attempting this? This is a requirement, as we are changing both the INF and the driver. I probably should have made a note of stating that, but as removing all USB devices is required for installing NUSB, and this was meant to be added to NUSB, I didn't think about it...

I have a special set of Slipstreaming Tools I purchased from RLoew. It allows me to Change/Add/Remove files in the CABs.

A Proposal/Suggestion for the Expansion of NUSB Hello, maximus-decim! My compliments on a great package for 98SE. I have a suggestion for a small "expansion" of NUSB, and I'd appreciate your thoughts on it. As some of you may know from other threads I have been working for a while now on building myself a "slipstreamed" installation of Windows 98SE. Over the past few days I have been working with getting NUSB integrated into my installation and I have made a couple of discoveries that I believe are relevant. Other threads relevant to this discussion: Some of you may also be familiar with RetroOS's thread about getting a USB Composite Device working in 98SE with NUSB (and in his case 98SE2ME.) And with Tihiy's thread that originated the USB2.0 stack for 9x. Do not install the USB20DRV package from this thread, it is listed here for reference in this situation only! After I had successfully integrated NUSB into my slipstream, I browsed through these threads for any relevant information about any further USB-related updates that I might integrate. After reading RetroOS's thread, I decided to take a look at USBCCGP.SYS. RetroOS stated that the Windows ME version of this file did not work for him. He searched for a 98SE and a Win2K equivalent of this file, and they do not use this file. Windows XP does, however. He went on to get various XP versions of this file to work on his system. In his case, 98SE2ME had copied the Windows ME version of USB.INF to his system, renamed to USBME.INF. This Windows ME .INF file calls for USBCCGP.SYS, and the combination of the Windows ME .INF and the Windows XP USBCCGP.SYS allowed him to get his device working. dencorso suggested in that thread that it might be possible to "merge" the 98SE and ME USB.INF's into a single file. In my case(for slipstreaming purposes), I needed to do this, so I did so. Now my custom USB.INF would call for and properly install USBCCGP.SYS. The next step was to examine the various versions of USBCCGP.SYS available. Keeping in mind that: 1.) the ME version did NOT work for RetroOS 2.) rloew had also informed me that he had trouble with the ME version of this file I tested the following versions on my 98SE system with the WDMCHECK utility: Windows ME (4.90.3000.1) XP RTM (5.1.2600.0) XP SP3 (5.1.2600.5512) XP KB945436 (5.1.2600.5585) ALL versions of USBCCGP.SYS have missing functions on Windows 98SE. BUT - they are missing DIFFERENT functions. The Windows ME version is missing the following functions: IoFreeWorkItem IoAllocateWorkItem The Windows XP versions are missing the following functions: USBD_ParseConfigurationDescriptorEx USBD_CreateConfigurationRequestEx Now, the missing functions of the Windows ME version MAY POSSIBLY be corrected by adding WDMSTUB.SYS that was previously a part of this package in an earlier version. However, the Windows ME version is documented to have problems. Here's where it gets interesting. The missing functions of the Windows XP USBCCGP.SYS can be solved by using the Windows ME version of USBD.SYS instead of the 98SE version. In RetroOS's case, as he had installed 98SE2ME, he had the ME USB.INF and the required ME USBD.SYS, so it worked. So here's the proposal. I feel that it would be a good idea to add the Windows ME USB 1.1 Driver Stack to NUSB along with the XP USBCCGP.SYS to expand its capabilities. It would involve adding the following files: ME RTM: OPENHCI.SYS 4.90.3000.1 UHCD.SYS 4.90.3000.1 USBD.SYS 4.90.3000.1 ME Q278289: USBHUB.SYS 4.90.3002.1 XP KB945436: USBCCGP.SYS 5.1.2600.5585 And a "merged" USB.INF file combining the contents of 98SE's USB.INF and ME's USB.INF. I have attached a copy of the one I made in case anyone wants to examine it. If you plan to test this you must remove ALL USB devices from the Device Manager FIRST! NOTE that to add it to a package it will need the "LayoutFile=" line removed and sections added for [sourceDisksNames] and [sourceDisksFiles] like USB2.INF in NUSB has. I believe that this addition would provide the best USB 1.1 and 2.0 support available for 98SE. I have tested installing these files in a VM, and everything goes smoothly, and WDMCHECK on that install reports no missing functions with any of those files. But I do not have a large selection of USB devices to test it more thoroughly. I welcome any comments or questions, I'll try to answer them as best I can. USBINF.ZIP