LoneCrusader

**EDIT 2-10-2010** In RE: Slipstreaming this Fix It appears that this issue cannot be fixed by slipstreaming. Slipstreaming does not allow the VMM32.VXD system file to be properly compressed during the first reboot. If the updated files are introduced to the system before the first reboot and the IOS error take place, WININIT will fail to combine various VXD's into VMM32.VXD.

I don't have any VM software installed (Yet). Ive used VMWare before at college, but it doesn't run on 9X. Haven't experimented with any others, although I bought a copy of Virtual PC 5 (on the box it claims to run in ME, so I'm hoping for 98SE as well ) on eBay the other day, just haven't had time to try it out yet. Also there is the 4GB FAT32 file size limit since I'm doing this in 98. I planned to make the ISO on a XP/NTFS or Linux system. Ill look into it again. Ill probably be back with a lot of questions

Using Plain El-Torito floppy emulation. Then I use JO.SYS for HDD/DVD boot choice, then the IO.SYS/CONFIG.SYS Menu to choose which system to install. Actually I did not create an ISO image, I just used MagicISO to burn the DVD. I planned to make an ISO of it later if everything worked properly after testing. I wouldn't be that sure, I see no theoretical reason against the fact that a BIOS may be able to boot from a no-emulation DVD and NOT from an El-Torito Floppy emulation one. Easiest to check would be to use a no-emulation bootsector, as an example grub4dos grldr, and then chainload the floppy image. Mkisofs is anyway recommended (though it has an awful syntax) as we know how it works. jaclaz Ugh, I was hoping to avoid having to decipher grub4dos. Although I see some advantages in it, I looked into it at the beginning of this project and decided to run away from it

Used WinImage 7 to create floppy image, Used MagicISO 5.5 to burn the DVD.

Ive been in the process of making a Multiple Windows installation DVD, using an image of a custom boot floppy (DOS/WIN9X style, not 2K/XP style) to make the DVD bootable. The floppy disk that I have used for the image boots properly every time, and if I write the image to a CD it boots properly. However, if I write the SAME bootable image to a DVD, it does not boot when the computer starts up. This computer has no problem booting from a Knoppix Live DVD, so I know there's not a hardware problem. I can choose "Boot from CD" inside System Commander, and it will boot from the DVD. This is useless on a computer without System Commander or a similar boot loader installed though. Any ideas?

Eureka! You have found it. Thanks for finding this, it was driving me crazy. The four Optional Components that would not install are: Audio Compression Sample Sounds Sound Recorder Volume Control That article suggests a solution, but I don't think it will work for me. It looks like I will have to manually check them during each install, as I always disable or remove the sound card (and NIC, Modem, USB, etc) whenever I install Windows so that I can re-enable or install them one at a time with the correct drivers.

I looked at the 1217 Version of Windows 95 VMM.VXD. Making a Version of my Patch for Windows 95 looks doable, but requies more extensive modifications, since it was designed for even less Memory than Windows 98. I do not have a Windows 95 Test Setup. I'll be your first volunteer If you're willing to give it a shot, I'll test it as many times as you need me to. I have copies of Windows 95 B and C, and the motherboard that I used for the processor test can use up to 2GB RAM. I have some boards that can use 4GB as well. I looked at VMM.VXD in my 95C setup and I have version 1216. **EDIT 2-10-2010** Incorrect information removed. VMM32.VXD was modified by the USBSUPP.EXE patch, it no longer has a Version tab and there are also VMM32.TMP and VMM32.o20, all modified/created on the day I installed that patch.

ok give me some feedback can test some things with the msbatch ... I post here if I have any success OOPS! 03:32 AM... ZzZzZZzz Good Night Good Luck, and Good Night

Actually the MSBATCH is mainly for my own use, I'm building myself a Multiple-Windows Installation DVD. I saw your post about the slipstreamer, I hope to get a chance to experiment with it soon. Slipstreaming is way above my head, at least for now. If you can do things like this I might have to give you some other things to slipstream haha

Sure, here's a copy of my 98SE MSBATCH.INF ; MSBATCH.INF ; ; Copyright © 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" NoDirWarn=1 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="LoneCrusader" Display=0 [Network] ComputerName=CHANGEME!!! Description=CHANGEME!!! 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 "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 The Locale and Selected Keyboard values in there are set for the US, and of course so is the TimeZone.

There are blank lines before each section, it should show up that way in the code box, it does on my Firefox?? As for a blank line after, the scripts created by both the 95 and 98 batch tools did not put a blank line there. The scripts I created for 98 and ME worked flawlessly, and this one works now except for these 4 "Optional Components" - all the other optional components work properly. I changed all of the section titles to uppercase because the sample 95 scripts used all uppercase section names. I dunno, at this point I'm willing to try anything ** EDIT 1-30-2010 4AM ** Tried adding OptionalComponents=1 to the [sYSTEM] section. Tried copying and pasting the OptionalComponents section out of SETUPLOG.TXT again. Tried putting the [OptionalComponents] section in mixed case instead of all uppercase. Tried all these things together. Still Nothing. This is maddening!

Thanks jaclaz, that second link was extremely helpful. I ended up starting completely over with this. I took one of the sample scripts from the Windows 95 Resource Kit and renamed it MSBATCH.INF, and it worked, so I went from there. Apparently Windows 95 does not recognize MSBATCH.INF properly if there are any sections like [batchSetup] or [Version] above [sETUP] in the script. So now I have a (for the most part) working MSBATCH.INF. Now it gets even more crazy. The thing works perfectly except for the [OPTIONALCOMPONENTS] section. There are 4 items in the Optional Components section that are never checked during Setup, even if I place a 1 after their name in MSBATCH.INF. I took this section directly from SETUPLOG.TXT on a previous install, and I have checked and rechecked the syntax & spelling of their names. Ill post my file here, maybe someone will see something that I don't. ; MSBATCH.INF ; Copyright © 1995-1998 Microsoft Corporation. ; All rights reserved. ; [SETUP] Express=0 InstallType=3 EBD=0 InstallDir=C:\WINDOWS ChangeDir=0 NoDirWarn=1 Uninstall=0 ShowEula=0 ProductID=xxxxxxxxxxxxxxxxxxxxxxx TimeZone="Eastern" [SYSTEM] Locale=L0409 SelectedKeyboard=KEYBOARD_00000409 [NAMEANDORG] Name="LoneCrusader" Display=0 [NETWORK] Display=1 Clients=VREDIR Protocols=NWLINK, NETBEUI, MSTCP ComputerName=CHANGEME!!! Description=CHANGEME!!! Security=SHARE [MSTCP] DHCP=1 DNS=0 WINS=DHCP [NWLINK] Frame_Type=4 [VREDIR] ValidatedLogon=0 [OPTIONALCOMPONENTS] "Accessibility Options"=0 "Accessories"=1 "Audio Compression"=1 "Backup"=1 "Blank Screen"=1 "Briefcase"=0 "Calculator"=1 "CD Player"=1 "Character Map"=1 "Clipboard Viewer"=1 "Communications"=1 "Curves and Colors"=1 "Defrag"=1 "Desktop Wallpaper"=1 "Dial-Up Networking"=1 "Direct Cable Connection"=1 "Disk compression tools"=1 "Disk Tools"=1 "Document Templates"=1 "Flying Through Space"=1 "Games"=1 "HyperTerminal"=0 "Jungle Sound Scheme"=1 "Media Player"=1 "Microsoft Exchange"=0 "Microsoft Fax"=0 "Microsoft Fax Services"=0 "Microsoft Fax Viewer"=0 "Microsoft Mail Services"=0 "Mouse Pointers"=1 "Multimedia"=1 "Musica Sound Scheme"=1 "Mystify Your Mind"=1 "Net Watcher"=1 "Object Packager"=1 "Online User's Guide"=1 "Paint"=1 "Phone Dialer"=0 "Quick View"=1 "Robotz Sound Scheme"=1 "Sample Sounds"=1 "Screen Savers"=1 "Scrolling Marquee"=1 "Sound Recorder"=1 "System Monitor"=1 "System Resource Meter"=1 "The Microsoft Network"=0 "Utopia Sound Scheme"=1 "Video Compression"=1 "Volume Control"=1 "Windows 95 Tour"=1 "WordPad"=1 "Flying Windows"=1 "OpenGL Screen Savers"=1 "Additional Screen Savers"=1 "Desktop Management"=1 "Imaging"=1 "Windows Messaging"=0 "Multimedia Sound Schemes"=1 "Microsoft NetMeeting"=0 [PRINTERS] Any more suggestions?

Thanks MDGx @everyone else: I'm open to suggestions on how this "patch" might be improved, If some of you get to test it, please give me some feedback. Good Luck!

**EDIT 2-10-2010** Incorrect information removed. This is possible if you allow the IOS error to be displayed and allow VMM32.VXD to be compressed before copying the K62 patch + NIDS.VXD. (See instructions above.) I strongly recommend installing DUN14-95.EXE normally when Setup is complete however, it contains several other updated system files related to Networking, whether you use Dial-Up Internet or not. Wow I never thought I would be worthy of that list. Thanks guys!

**EDIT 2-10-2010** It does not appear to be necessary to do this. I have changed the instructions to reflect that. Congrats, I'm glad someone else is interested and can confirm my results. I might have to try my hand at making a "patch" that would automate some of this if people are interested. Now if only RLoew's RAM patch worked in 95

***UPDATED 06-10-2013*** I have managed to fix the 2.1GHz CPU limit of Windows 95. Completely with updates from Microsoft... when they claimed there was no fix for this. Here's a link to the MSKB article on this issue. Q312108 - Windows Protection Error in NDIS With a CPU That Is Faster Than 2.1 GHz -------------------------------------------------------------------------------------- Version 3.0 Released 06-10-2013 New or otherwise significant in this version: - Version 3.0 can be used on all Windows 95 versions. (RTM\OSR2) (95\95A\95B\95C) - Version 3.0 addresses specific issues with and better supports Windows 95 RTM. (95\95A) - Version 3.0 makes the proper registry entries that would be made if AMDK6UPD.EXE and the other updates were installed under Windows 95. - Version 3.0 includes a Processor-specific HotFix for Windows 95B OSR2. It is not needed on other versions of 95. - Version 3.0 no longer includes or mandates the installation of DUN14-95.EXE. Still "recommended." - Version 3.0 can be installed before or after the "Windows Protection Error in IOS" has been displayed. (Before is still the preferred method.) - Version 3.0 can patch a Windows 95 installation in directories other than C:\WINDOWS. - Version 3.0 includes further updated versions of some system files contained in the AMDK6UPD.EXE patch, rendering AMDK6UPD.EXE obsolete. - Version 3.0 includes PTCHCDFS, a free update by Rudolph Loew that corrects the displayed size of DVD media. -------------------------------------------------------------------------------------- The README.TXT from FIX95CPU_V3_FINAL.ZIP, provides a detailed overview of this project, this issues it addresses, and the instructions for getting it to work. I will post it here: ------------------------------------------------------------------------------------------ Windows 95 High-Speed Processor Support v. 3.0 By LoneCrusader CONTENTS OF THIS PACKAGE: README.TXT - Self Explanatory. FIX95CPU.EXE - Self-Extracting Bootable Floppy Disk image. FIX95CPU.IMA - A standard image of the Bootable Floppy. (For Virtual Machines.) FIX95CPU.ISO - A standard Bootable CD image. (For Virtual Machines, or systems without a floppy drive.) VMM2XUPD.EXE - HotFix with updated VMM.VXD's for Windows 95 B OSR2. (Install in Windows 95 B OSR2 after Setup has completed.) ----------------------------------- NOTE: The first section of this README will explain the issues addressed by this patch. If you are familiar with these issues, you may skip to the second section for step-by-step instructions. SECTION ONE: Windows 95 has two specific errors when dealing with processors with speeds higher than 350 MHz. With a little patience however, both of these errors are fixable. The first error occurs with processors greater than 350 MHz. Microsoft released a patch for this error, AMDK6UPD.EXE. This patch IS NOT just for AMD processors. It will work for Intel Pentium 4 processors as well. The problem with Microsoft's patch is that it must be run from within Windows. When your system encounters this error, you will not be able to boot into Windows. This error will be displayed on the first reboot during the installation process. Here is the text of the error: While initializing device IOS: Windows Protection Error. You need to restart your computer. The only way to fix this error is to manually install the files contained in the Microsoft AMDK6UPD.EXE patch. This package automates the process for you, so I will not go into further detail on that issue here. The second error occurs with processors greater than 2.1 GHz. This problem also affected Windows 98 (First Edition), and Microsoft issued a HotFix for Windows 98, but not for Windows 95. According to Microsoft, there is no fix for this problem in Windows 95... WRONG! This error is very similar to the previous one, and it will also be displayed on the first reboot of the install process, after you have fixed the previous error. Here is the text of the error: While initializing device NDIS: Windows Protection Error. You need to restart your computer. This error is corrected by an updated file contained in the DUN14-95.EXE Dial-Up Networking 1.4 Update for Windows 95. This package automates the process for you, so I will not go into further detail on that issue here. NOTE: This update renders the AMDK6UPD.EXE patch OBSOLETE, as it installs newer versions of some system files contained within AMDK6UPD.EXE. While the main purpose of this update is to enable the use of High-Speed Processors, I decided to include any available newer versions of the system files already contained in this patch. List of Issues (MSKB Articles) FIXED by this update: Q192841 - Difficulties Using AMD K6-2 or Athlon Central Processing Unit Q234259 - Revision to AMD K6-2/350 Central Processing Unit Update Q312108 - Windows Protection Error in NDIS with CPU Faster Than 2.1 GHz Q231942 - Cannot Undock Notebook Computer with LS-120 Removable Drive Q175629 - Large IDE Hard Disk May Run In Compatibility Mode Q274175 - Error Opening/Copying File/Folder Eight Levels Deep on CD-ROM Q159153 - Error Messages While Backing Up to Some Floppy Disk Drives This update also includes a patched version of CDFS.VXD using PTCHCDFS, a free update by Rudolph Loew (rloew) to fix the incorrect size value (1.99GB) reported by Windows 9X for DVD's. A separate bug exists in Windows 95 RTM/A that causes DVD sizes over 4GB to not have their byte counts displayed properly, showing "---" instead, but the correct total size of the DVD will still be displayed. Installing other update packages for Windows 95 RTM/A may yield a solution to this, but has not been tested. Also included in this version is a HotFix, VMM2XUPD.EXE, which installs the latest version of VMM.VXD for Windows 95 B OSR2. This package should be installed when Windows 95 B OSR2 Setup has completed. This update will not run on Windows 95 RTM/A and is not required on Windows 95 C OSR2.5. Credits & Other Information: Rudolph Loew has also created a free UDF filesystem driver for reading UDF formatted CD's/DVD's in Windows 95. It can be obtained from his site at: http://rloew1.no-ip.com or mirror at: http://rloew.limewebs.com Many thanks go out to Rudolph Loew for his assistance with this project! Credit also goes to Petr at MSFN for providing patched files for 95 RTM. And finally credit to Queue at MSFN for creating the ANSI Windows Logo. For further information and updates, visit this topic at MSFN Forums: http://www.msfn.org/board/index.php?showtopic=141402 This package makes use of the General Replace (GR) text replace utility created by Andrew Sharrad, which can be found at: http://www.sharradsoftware.co.uk SECTION TWO: Follow these Instructions to get Windows 95 up and running. You Will Need: Blank Floppy Disk or Blank CD Files Contained In FIX95CPU.ZIP NOTE: If your system does not have a floppy drive, the FIX95CPU.ISO Bootable CD image in this package can be used (with Nero or a similar CD burning program) to create a bootable CD that can be used instead of a floppy. NOTE: These instructions and the FIX95CPU installer assume that you are installing Windows 95 to C:\ Drive, however you can use a directory other than C:\WINDOWS. 1. On another computer, use the self-extracting Floppy Disk image (FIX95CPU.EXE) or the Bootable CD image (FIX95CPU.ISO) provided in FIX95CPU.ZIP to create a custom Boot Disk that will contain this patch. 2. Prepare your system and run Windows 95 Setup. 3. When Windows 95 asks you to Restart, insert the Boot Disk or Boot CD that you created with the enclosed image, and click Finish. You should have the Boot Disk or Boot CD inserted BEFORE Windows Setup continues and the IOS error is displayed in order to speed up the boot process by combining .VXD's with WININIT.EXE, but this version allows for installation after the IOS error has been displayed. 4. The Boot Disk will start your computer in DOS mode. Press SPACE and you will be given an opportunity to view this README file. Choose Y or N, and then all you need to do is press SPACE again to bring up the next page of the README, or to apply the patch. The program will output its actions to the screen so you can see what is being done. Pressing CTRL-C at any time will terminate the FIX95CPU program. 5. When finished, press SPACE to reboot your system, then remove the Boot Disk or Boot CD so Windows 95 Setup can continue normally. If you are installing Windows 95 RTM/A or C OSR2.5, you are finished. For Windows 95 B OSR2 ONLY: 6. When Setup is complete and your Windows Desktop loads, run VMM2XUPD.EXE to update VMM.VXD to the latest version, and you will be prompted to restart. This update is not necessary on Windows 95 C OSR2.5. If you have Windows 95 RTM/A or C OSR2.5, skip this step. The VMM2XUPD.EXE will not install on Windows 95 RTM/A. The VMM2XUPD.EXE update addresses the following issue: Q179897 - Memory Management Problems with Pentium Processors You have successfully completed all steps. Install the drivers for your hardware and your programs. Have Fun! ----------------------------------- KNOWN ISSUES: 1. If you plan to install the Microsoft USB Supplement to Windows 95 OSR2 (USBSUPP.EXE), be aware that this update will sometimes overwrite the file C:\WINDOWS\SYSTEM\VMM32\NTKERN.VXD without prompting you to keep the newer file already installed by this patch. If this occurs, the following error will be displayed: While initializing device NTKERN: Windows Protection Error. You need to restart your computer. This can be corrected by recopying the NTKERN.VXD contained in this patch to your system. ----------------------------------- LEGAL INFO: THIS SOFTWARE IS PROVIDED FREE OF CHARGE WITH ABSOLUTELY NO WARRANTIES OR GUARANTEES. BY USING THIS SOFTWARE, YOU AGREE THAT YOU USE IT AT YOUR OWN RISK AND OF YOUR OWN FREE WILL. THE AUTHOR(S) OF THIS SOFTWARE SHALL NOT BE HELD LIABLE FOR ANYTHING RESULTING FROM THE USE OR MISUSE OF THIS SOFTWARE. IF YOU MODIFY THIS SOFTWARE, PLEASE REMEMBER TO CREDIT THE ORIGINAL AUTHOR(S) FOR THE ORIGINAL CONCEPT(S). ----------------------------------------------------------------------------- This software brought to you by Conner McCoy (LoneCrusader) with assistance from Rudolph Loew (rloew). ----------------------------------------------------------------------------- ------------------------------------------------------------------------------------------ ***UPDATE 12-18-2010*** Slipstreaming instructions added Here. Microsoft issued a Hotfix for this problem in Windows 98 FE. It contains an updated version of NDIS.VXD that only works in 98. Apparently they forgot (intentionally? ) or never realized that the updated version of NDIS.VXD in the DUN14-95 update solves this problem as well. Of course this isn't going to do you much good if Windows 95 drivers do not exist for your hardware. If you have version 3.40.1001 of the Intel Chipset INF Installation Utility, it still contains 95 Drivers covering the 845 chipset, which I know was used on motherboards supporting up to 3.06GHz processors. The system used for this test: -------------------------------------- Motherboard: Soyo SY-P4I845PE Processor: 3.06GHz Intel Pentium 4 w/ Hyper Threading Memory: 512MB Kingston DDR 333 Video Card: ATI Radeon 8500 LE 128MB Audio & LAN: Onboard

I actually assumed this would be an issue from the start. So while I created the initial file with 98, I hand-edited it for 95 and ME. The main differences are the Optional Components, and 95 uses "ProductID" instead of "ProductKey." I ran the 95 version of BATCH, and it created a file named BSETUP.INF which SHOULD have worked, but it doesn't, even when called specifically as an option. ( SETUP -s BSETUP.INF ) The 95 Setup program crashes with an error saying "Unable to find section" or something like that. I looked over the contents of the file, and it seemed to contain everything that was relevant. I actually had already checked out those pages except for the netsetup one, Ill have to look into it.

I extracted layout.inf from precopy2.cab and took a look at it, there is no listing in it for msbatch.inf. Some Google searches regarding this returned a lot of irrelevant data, mostly dealing with using a 95B/C disk to upgrade 95A. Do you remember how it was supposed to be referenced? I have noticed a small inconsistency between the sample .inf files provided on the 95 CD (95 Resource Kit) and the msbatch.inf that I generated with Batch98 (on the 98SE CD, which worked for 98/ME). I've not had time to investigate further, but Ill post the results as soon as I can. A bit off topic, but for the record, I once managed to get 95 running on a 3.06 GHz P4 machine. Used the AMDK6UPD patch to get by the 350MHz+ processor bug, and then deleting 2 files will get you around the 2.1 GHz processor limit that's referenced at the Microsoft KB. I haven't played around with it in a long time, I might have to try it again just for the heck of it.

@rloew, jaclaz, dencorso: Are there any more tests that we need to run on the 8GB drive, or any other information to be gathered from it for future reference? If not, I think I will repartition and reformat it using the method that dencorso suggested, I prefer the idea of having a DOS type boot sector instead of a NTLDR one, and this will hopefully also correct the odd CHS/LBA values. I've Hex-Edited maybe 2 files, so I don't quite trust myself yet to try fixing the partition that way. IMHO, Considering the odd partition values exhibited by both of my Kingstons, I believe that we should recommend repartitioning & reformatting new flash drives somewhere in the threads dealing with NUSB and/or other USB driver stacks. I know this is not really an option for those who already have data on their flash drives, but it might save some people with new ones from the problems that have been documented here. What are your thoughts?

If you don't mind spending $20, I recommend RLoew's patch. I've been using it for over a year now, never had the first single problem with it. Supposedly there are other ways of doing it, and others on this forum apparently have done so, but I never managed to get any of them to work. Good to see another 9X/ME user

You can't be serious. First, if you didn't have some information relevant to my question, why did you post in my thread? Second, Windows 95 is not and never has been "crappy." 95C is so far ahead of 98FE it's not even funny. Third, whether you or the idiots at Microsoft like it or not, Windows 95 put Microsoft at the top of the OS market. They owe a lot of the success they have to the Windows 9X family. They'd like to forget that Windows 95/98/ME ever existed, because they were more popular and generated more success for them than their pet Windows NT. Windows 95, like it or not, is a very important piece of computer history, and deserves a LOT of respect. So, unless you have some information relevant to my question, blunder back to the XP\Vista\7 forums.

Ive been trying to make a MSBATCH.INF file for Win 95C OSR 2.5, and not having any luck. I have successfully created them for 98SE and ME, but Win95 setup seems to completely ignore my file. I've read the articles in the Microsoft TechNet Library on automating Windows 95 installs, searched several pages on the net, and I searched 25+ pages deep in these forums for msbatch.inf "Windows 95" So I thought I would see if anyone here knows what the problem is, or has a working msbatch.inf for 95 that they wouldn't mind to let me take a look at.

Ran ScanDisk again, got same error, chose to Ignore. After that, ScanDisk finishes normally: It seems that ScanDisk is seeing the correct amount of used space, however, the exact same incorrect value is still displayed in the "Properties" tab in Explorer. Do you need me to image the first 16mb of the disk? Don't worry, the drive we're working on now is brand new and blank. This one's all for science, haha So maybe we can get to the bottom of these bizarre flash drive errors. I'm beginning to think that the first thing to do after buying a new one is to repartition it and reformat it, so that way you know it will have "normal" settings

Ok, how's this? K8GB8192.7z

Partition Saving didn't let me choose a sector count, so I set the split file size to 4mb and stopped it after the first one. If this doesn't work, or isn't what you need, Ill try something different. EDIT: Bad file removed.