rloew

To be even pickier, the Drive Letter Assignments in NT Systems can be changed by the user. My point was that Windows 9x needs to match the DOS Drive Letter assignments so the DOS Drive Letter Table needs to be carried over to Windows. Windows cannot determine the Letter Assignments on it's own because they are affected by BIOS settings that are not visible to 32-Bit Code.

Since Windows 9x provides a functional Pre-Windows DOS environment, think CONFIG.SYS and AUTOEXEC.BAT, it needs to provide the same environment while in Windows. This requires it to retrieve some information from DOS. There is very little, if any, DOS Code actually run by Windows, except for Setup, unless you have unrecognized TSRs or missing 32-Bit Drivers. There is a significant amount of 16-Bit Code carried over from Windows 3 but it runs in Protected Mode, not Real or Virtual Mode. Non-UEFI Windows NT Software has to use 16-Bit Code to Boot itself and tries to switch to Protected mode as fast as possible. There are a number of consequences to this. If you run File Manager or Virtual DOS, the Drive Letters will often not be in the same order as in DOS. If yoiu do not have a Driver for something, you will have no functionality at all, rather than the limited Functionality of Compatability Mode. Also many changes to the Boot Hard Drive, that Windows 9x can handle, will make Windows NT unbootable.

Windows 9x is not hard coded into the Desktop. Add COMMAND to your AUTOEXEC.BAT and you will see. You can still run WIN to go to Desktop. The difference is that exiting the Initial COMMAND.COM runs WIN automatically. Windows uses DOS to Bootstrap. Once running it does not depend upon DOS except for Compatability Mode Functions.

The SATA Patch should woirk.

A DOS Driver might work if it can be run in compatability mode. I have never tested this so there are no guarantees.

Updating what I said previously, Windows 9x runs in the Core handed to it by DOS, not necessarily the BIOS. I am writing this on a Windows 98SE System running from the second Core, an AP (Application Processor) not the BP.

Breaks the execution of the only vbscript I use. Until a proper fix can be made, something had to give.Microsoft's workaround was to disable VBScript entirely. In oleaut.dll 4520 the same string is located at 29f20. I suppose I can use the fix for this version as well ?Probably.As long the string appears only once and in this area, it will probably work. It will not work on XP+ Files.

Breaks the execution of the only vbscript I use. Until a proper fix can be made, something had to give.Microsoft's workaround was to disable VBScript entirely.

The following Patch will disable the specific function involved. OLEAUT32.DLL 2.40.4518.0 29E90: 83EC14538B5C241C -> B80D000280C20800

I have seen the issue with resources in some Computers when only one IDE channel is in use. It appears that the BIOS frees up the Interrupt when it doesn't detect any Drives on the Secondary Controller. It is then assigned to other Devices. Windows 9x does not detect this and tries to assign it to the Secondary Controller causing the conflict. Disabling the unused Channel is a perfectly acceptable solution until you add more Drives.

Writing Multi-Threaded Software allows the program to take advantage of Multiple Cores when run under a Multi-Core aware OS. The same Software can run under Windows 9x but the speed advantage will be lost. If such a program cannot run under Windows 9x, it was explicitly designed to require Multi-Core or uses other features that Windows 9x does not have. The reason there are so few programs is because the writers chose to abandon Windows 9x.

Is the Hard Drive SATA or PATA? Are you using a 48-Bit LBA Patch? If not: Is the 40GB Windows 98 Partition within the first 137 GB of the Hard Drive? Is the upper part of the Hard Drive Formatted as FAT32 or NTFS?

With all due respect, and just to avoid any misreadings of your above statement, and considering that hyperthreading provides two Hyperthreads per Core, I understand what you just said means "Win 9x knows about and uses one single Hyperthread from just one Core, and nothing more, regardless of how many Hyperthreads and Cores may exist in any given processor it's running on"... and that means you're confirming, albeit in a more detailed way, the other replies preceding yours, mine included, right? Correct.To be even more precise, THE Hyperthread in THE Core of THE CPU handed to it by the BIOS. Normally this would be the BP (Base Processor) designated by the Hardware.

Windows 9x knows about and uses one Hyperthread in one Core. The Kernel is not reentrant enough to be able to add Multi-Core support. Applications can be written to use more Cores but they have to manage the Cores themselves. I have written a Multi-Core API for application writers to use. Unfortunately the big Software companies have abandoned Windows 9x completely.

Without third party Drivers for those Controllers, if you have more than one, you probably need the SATA Patch.

I'm not sure the reason why from your descriptions but you may need my SATA Patch to restore ESDI_506.PDR.

I already developed a Mass Storage Driver. Mass Storage Drivers are not responsible for USB 2 Support. A separate USB 2 Controller Driver is required. The existing USB 2 Controller Drivers were not designed for Windows 95. LoneCrusader and I are working on the problem but success has been very limited.

USB 1 Mass Storage Devices are supported in Windows 95. See the XUSBSUPP Thread in the Pinned Member Projects Section for the necessary Drivers. USB 2 is not currently supported, nor are Keyboards and Mice. LoneCrusader and I are still working on it.

I use my own tools for working with LE Files. I only just created a Source file for NTKERN.VXD a few days ago. Analysis will take a lot longer.

What are you trying to do? LoneCrusader and I have been working on this issue for more than two years.

That would limit you to a narrow range of Motherboards as older ones do not have SATA and newer ones use Chipset based SATA with no Windows 98 Drivers. The PCI-E solution is for people who want to add more Drives. Then you have paid roughly the same price, or more, for a solution that provides only two ports and ties up a PCI slot.

My SATA Patch works with all Motherboards SATA Controllers I have tested and with most PCI-Express SATA Cards.

As written where?AFAICR the Xeno port to Windows 9x worked (on some hardware). I downloaded the versions you linked to. For one thing there is no INF File for Windows 9x. Why not? Because business of can openers manufacturers may (hypothetically) become at risk ? (though only a few of them remain, I don't think they are registered as "protected species" ) jaclaz Because it won't help open the can.

Well, then you will have to thank me (and the OP is very welcome to unthank me ).jaclaz As written, it clearly cannot work properly on Windows 9x, so the thanks may be premature. I did say "Maybe".I will recommend that an "Unthank" button be added to the Forum software. Next time someone asks for help opening a can, don't send them an engineering drawing of a can opener.

I downloaded the Windows Update Catalog for ME years ago. I got 53 Files. This does not include the IE6 SP1 package for ME. Not all of them appear to be useable or needed. au15.cab crlupd.exe directx_9c_redist.exe dotnetfx.exe js55men.exe MDXSetup.exe MPSetup.exe msjavwu.exe setup.exe wm9codecs.exe 273017.EXE 273991.EXE 274113usam.exe q279328.exe 290700.EXE Q317244.exe wm320920_64.exe wm320920_71.exe NDP10_SP_Q321884.exe 323172_ME.EXE 323255_ME.EXE 329048.EXE 329115_ME.EXE q329414_mdacall.exe 811630USAM.EXE 812709USAM.EXE WindowsMedia71-KB817787.exe IE5.5sp2-KB823353.exe 823559USAM.EXE Q823718_MDAC_SecurityPatch.exe WindowsMedia-KB828026.exe DoomCln-KB836528-v4.exe NDP1.1sp1-KB867460.exe NDP1.0sp3-KB867461.exe 888113USAM.EXE KB891711-v2.EXE IE-KB891781.exe KB896358.EXE KB904706-DX8.exe KB904706-DX9.exe KB908519.EXE MDAC28RTM-KB911562.exe MDAC28SP1-KB911562.exe KB913433.exe KB917344.Exe WindowsMedia9-KB917734.exe KB918547.exe q813951.exe KB833989.exe KB837009.exe KB887797.exe KB916281.exe KB918439.exe