SweetLow

It depends of software you try to run, to be precise. Few options: 1. HARDWARE Registry Subkey (HKLM\Enum\). Search registry keys with name == "PORTNAME" 2. BIOS Data Area, 40h:0 - 40h:7, 4 WORDs, BIOS known COM port base addresses.

You probably misunderstand the problem. Software get the right mode (which it requested), but hardware output to monitor has different mode (resolution) because between software visible surface and hardware output locates the scaler. The question is how to eliminate it.

1. It is not Nvidia specific behaviour. BIOSes of old ATI cards setup 1280*1024 on DVI output for example no matter what is native resolution of monitor (if it is above or equal to 1280*1024, of course) and requested video mode. 2. Only patch BIOS or direct program GPU.

Yes. But I assume "label" command does its work still... If you will point me why do you need variable label when driver create volume I do option for this. > Do you need a separate 16-bit client? No. Drive can or can not be mounted before. readme related options: - checking for third-party drives in memory at start address: "CheckExternalVolume"=hex:FF enabled by default. If a drive is detected, there are two options (by configuration) - it is either used or left under the control of the of the old software, with use option enabled by default: "GrabRMVolume"=hex:FF "GrabExternalVolume"=hex:FF. The first parameter defines the use of known DOS drives (e.g. RAMDSK32/64), the second - all other drives (no examples yet) i.e. GrabRMVolume - use DOS mounted drive, GrabExternalVolume - use unmounted volume, no matter how it was loaded into memory

For 9x modern version of hardware accelerated access interfaces exists: Direct Draw DDI & Direct 3D DDI available in ME DDK.

Attention grabber? My friend, if you want to see what is attention grabber look at hidusbf... Yes, subject is not the last thing in my TODO list.

There is minor error in himemex, i described it on ru-board. I recommend you read there too.

As with any PM only drive - in Device Manager made it Removable, set letter, made it non Removable. And as drive can stopped and started in Device Manager - no reboot needed (if no swap file on this drive, of course). >It seems that this is the first full-fledged PSE ramdisk in history that installs and works directly under WINDOWS! The first PSE drive for Windows was made by Intel for Windows NT 4.0 ~ 25 years ago >It would be nice if someone (who already uses such hardware) checked this right away. You have to know already that I'am running one of my Windows 98 SE on Core i7 10700... >the question also arises of the compatibility of RAMDRV4M with more promising hardware There is no problem for compatibility for pure protected mode software. The problem of RLoew's solution is transition from real mode code that drives something to protected mode code that access memory and back. >and a message appeared on a blue background "Windows The volume that was removed had open files on it. Next time please check first to see if the volume can really be removed. Press any key to continue." Read readme... > Is it really in RAM? Read readme...

ramdrv4m - Universal RAM Drive for Windows 9x https://github.com/LordOfMice/Tools/blob/master/ramdrv4m.zip Features description: 1. Memory support above 4GiB (default mode). Primary purpose of creating this software. 2. A full-fledged 32-bit protected mode driver. 3. High speed of operation. 4. Can utilize RAM Drives created in memory by other software. In particular, it is compatible with RAMDSK32/64 from RLoew. 5. It consumes only 4MiB of virtual address space. In addition to the real memory used for RAM Drive itself, of course. 6. Works on Pentium and higher class processors (i.e. it does not work on 80486). As usual - readme is your best friend...

Ok.

Flashing to Quadro to work in 2000/XP? Something is very bad with your logic.

And what? You supported off-topic no matter am I admin or not.

Of course, but you wrote hard off-topic for THIS thread.

The package for A20 Line Always On processing (and more) in HIMEM.SYS http://sweetlow.orgfree.com/download/a20alwon.zip Joint work with BolenB As usual - do NOT forget to read readme

Win9x VCACHE Protection Error Fix (.VXD version of CREGFIX.COM), primarily for Windows ME https://github.com/LordOfMice/Tools/blob/master/cregfix.zip I tested it on Windows 98SE so IDK if it actually works on Windows ME.

Yes. With this flag cleared kernel mode code is ignoring the fact that page is read-only and writes on this page successfully.

The best expirience is test it youself if you doubt. But i didn't believe in this fact too: http://forum.ru-board.com/topic.cgi?forum=62&topic=28114&start=5240#17 (translate the P.S. from this post) P.S. And i can demonstrate few other (registry) options which i found when i really need them

Ok, may be in some cases (not my case, NForce2 PCs work with ACPI flawlessly). But in any case "without ACPI" and "setup /i" are NOT the same things.

Why so? The PCs from 98-ME era are supported ACPI that is working in 98-ME, eh.

It is possible before and (much easy to do) WHEN Windows starts. ACPI driver in Win98 supports overriding of ACPI tables through the Registry. 1. mercury did the patch to win.com to run additional software on exiting from Windows which in turn can power off PC 2. without any patch you can do the same thing just running above mentioned software in MS-DOS Mode n.b. - both questions are offtopic for this thread p.s. I edited my previous post

1. Try to access drive from other file manager - far, total comander or else. 2. Is this drive accessible on the same PC from other OS like XP? RLoew did 64-bit LBA patch for SCSI and I wrote driver for the same (USB drives are SCSI from protocol view point), but 500GB drive has to use 32-bit LBA and does not need any patch by default.

>in My Computer First check that CD-ROM drive is present in Device Manager after reboot (better in hardrware tree view mode, of course).

https://github.com/LordOfMice/Tools/blob/master/rmmremove.zip Utilities for removing "bad" DOS (RMM - Real Mode Mapper) drive letters for Windows 9x. Some analogue of "dlmanip delete" for DOS. Contents: RMMFLRM.VXD Delete phantom floppy drive letters. RMMBADRM.VXD Removal of USB drive letters processed by BIOS and visible as a duplicate under Windows 9x after Hand Off for USB controller. RMMLTRRM.VXD & RMMLTRRM.REG Remove any drive letter, including both boot and system letters (if you want to check this), not automatically, but by arbitrary list in the registry (RMMLTRRM.REG). N.B. These tools really delete drive letters, not just masking in Explorer:

I checked ReactOS image - and all is working as expected without any errors: copy and mount of image (on USB NTFS drive, on ATA NTFS drive and on ATA FAT32 drive).