rloew

Useful to me? Maybe. Useful to the OP? I doubt it.

Add Windows ME to the list of OSes. I solved the Installation problem I previously had.

I have completed setup of a new Z87 Intel System. OSes: Windows 98SE / MSDOS 7.10, Windows 7 (32-Bit MBR, 64-Bit MBR and 64-Bit UEFI), Windows 8 (64-Bit MBR and 64-Bit UEFI), UBUNTU Linux 14.04.1 (32-Bit MBR and 64-Bit UEFI). RFDISK Extended Multi-Boot Profile MBR + GPT. Memory: 32 GiB (4x 8 GiB DDR3 DIMMs; 3464 MiB available to Win 98SE; 29182 MiB available to RAMDISKs and 64-Bit Memory SDK) Motherboard: MSI Z87-G41 CPU: Intel Core i7-4770K Eight Core Video: Default VGA Only at present Sound: None at present Ethernet Card: RTL8111E (buggy Tenda Driver) 3 Removable SATA Trays 4TB SATA Hard Drive currently installed SATA Blu-Ray Writer TBPLUS Disk Package CONFIG.SYS: DEVICE=C:\HIMEMEX.SYS /S /V ; used with RAMDSK64 and 64-Bit Memory SDK. DEVICE=C:\WINDOWS\HIMEM.SYS /NUMHANDLES=64 AUTOEXEC.BAT: SPLIT8MB RAMDSK64 T: 6000000 (6GB non-XMS RAMDISK For Internet Temporaries) Remaining 64-Bit RAM reserved for 64-Bit RAM and Multi-Core SDKs. vmm32.vxd (real mode), vcache.vxd: 4.10.0.2222, vmm.vxd: 4.10.0.2226 with RAM Limitation Patch 7.1 (with /M and /P Options plus SPLIT8MB)

I have successfully installed Windows 98SE on a MSI Z87-G41 Motherboard with an Intel Core i7-4770K CPU. To Install Windows 98SE: You will need to add your own Video, Audio and probably Ethernet Cards. Use "SETUP /p i" to avoid ACPI Problems. You will need my SATA Patch. I have found an Ethernet Driver that works with the built-in Ethernet but it reports errors and only supports 10/100. You will need my RAM Limitation Patch with the /M Option and SPLIT8MB if you use it. A similar approach will allow the installation of Windows ME.

Not totally stupid. Once in a while it works. Sometimes there are associated settings that can be fixed, but most of the time the trick is to find a useable Driver Sometimes Windows 2000 Drivers will work.

Unfortunately you can't just add NT Functionality without risking 9X Functionality. Many NT API Functions are different in ways that are not compatable. I have even seen Calling conventions changed such as FASTCALL to STDCALL. This makes it virtually impossible to fully support both.

As far as I can tell, putting a valid bootable MBR on the USB Key is sufficient to get it to boot with most BIOSes.

Do you have the card, if so have you tried it with the above files?It worked fine for me on ME, used Opera quite a bit through the wifi. There's an entry for NdisQueryBufferSafe in the .sys file, looked for it with a hex editor. cheers, Pete. Is editing a sys file to change NdisQueryBufferSafe back to NdisQueryBuffer possibe/allowed? I'm comparing a 9x driver to NT-looks like it's the only difference. I don't have software to save the changes made to a sys file. Changing the name will not work. The two Functions have different numbers of arguments. A small Kernel Mode translation routine would need to be hooked into the WDM Export Tables.

The entire installation can be done on SATA, but the procedure is much more complicated, especially on Windows ME.

My SATA Patch has to be installled after any 128GiB Patch except my own High Capacity Disk Patch. The same is probably true for the Service Pack as well.

My Patches need to be installed in safe Mode on Windows ME or from a Bootable DOS Floppy. Preventing SFP from possibly undoing the Patches would require removing the affected files from the list SFP maintains.

Your problem is definitely due to the SATA Drives. If you limit yourself to 4 Devices you may be able to get it to work. My SATA Patch would allow you to use Native Mode SATA and eliminate this restriction. I also have a Patch that would allow you to use 2GiB or more of RAM.

Having SATA drives can cause Windows to hang. Enable logging and report the last line in BOOTLOG.TXT.

Well, RLoew's SATA patch costs US$11 (which is about £6.50), and arrives by e-mail right after you pay. All the wait and effort involved saved you about £1.50. Is it worth it? Not much in it, really. I guess at least with the adaptor I am less likely to lose it. Not likely.I don't charge for replacement copies. You also have to pay by the Drive if you use those adapters.

Possibly. I would need more information. Can you tell me what process is doing the Read that crashes? I also need to know when the crash occurs. I am not familiar with INFmon and don't see any obvious references on Google. I use FILEMON and REGMON.

The download is on Microsoft's website. Google: WindowsXP-KB2964358-x86-custom-ENU.exe to get the page. There are 4 imports in the Installer that need to be stubbed before it can be run.

I never said it was a "full" alternative to NUSB, but it is a "full" alternative with respect to the OP's question.I was not aware of the "Wintricks" alternative until you mentioned it today. If you check my timestamps, I created my version at least 18 Months before the Wintricks Version was posted to MSFN. Also I don't read Italian.

For the record BOTH drivers .sys and .pdr are EXACTLY the same, there are only some (it seems to me like very marginal, i.e. related to the driver name in the GUI ) differences in the .inf install file, not really "an alternative", but rather "another copy".And still for the record, these are "plain" and "language independent" USB drivers for 98, while NUSB is a more complete (and complex) set of files including a full USB stack, and - at least last time I tested it - seemed like "language dependent". jaclaz It is exactly what I stated it was supposed to be. A Generic Mass Storage Driver. It was never intended to be be a full USB Stack.It is not "another copy" as the original was not configured as a Generic Driver. The INF is an integral part of a Driver Package. Most of the work I did was selecting the best Driver from a whole collection of Manufacturer Specific USB Drivers that I had. Many of them had eccentricities that made them not work with various Devices. It is a perfectly valid "alternative" to NUSB if you only need to add a Generic Mass Storage Driver.

I am writing this using Windows 98SE on *precisely* that Motherboard. I needed to add a Video and Sound Card, but everything else works with my Patches. I have more RAM, bigger Hard Drives and one less Core. No SSD.

Be my guest. The money you will save is far less than the minimum wage for the time you will spend.

Yeah, I wouldn't know how to "realign" a system file I'm afraid. That and I feel it's only fair that a publicly known way to "rescue" the logo from the "prison" that is IO.SYS is revealed. I see nothing especially fair about that. I consider it one of my Trade Secrets.

The LBA48 issue applies to SATA as well as PATA. SATA supporting BIOSes are new enough not to have the LBA48 problem but Windows 9x still would. The LBA48 Patch is separate from my SATA Patch. Partition size is not limited by the LBA48 issue, total disk size is. Windows 98 SCANDISK/DEFRAG is limited to 128GB Partitions. Use Windows ME SCANDISK/DEFRAG for larger Partitions.

The easiest way to make the change is to copy the compressed Logo from the Windows 98 IO.SYS to the Windows 95 IO.SYS. Some realignment will be required as the 98 Compressed Logo is larger than the space allocated to the 95 Logo. I'm not sure why you would want to use the Windows 98 Logo in your Windows 95 System. It says "Windiows 98".

The 149GB report is not an issue. 160GB = 149GiB. Some BIOSes report GB, some report GiB without making it clear which The LLXX Patches do not support SATA, only large hard drives. Resolve your ACPI Problems and retry the BOOTLOG.TXT test.

I have extracted the LOGO from IO.SYS 7.1. I used the decompression code built into IO.SYS. This is how IO8DCOMP works. The LOGO can also be removed reducing IO.SYS to 156,216 Bytes. Incidentally, my IO.SYS fix has nothing to do with the LOGO.