deomsh

@~♥Aiko♥Chan♥~ Did you try Gom player 2.0.12.3375? It's listed for win95 (didn't test it).

Missed this post. Please can you explain ADIXctlLevel, ConservativeSwapFileUsage and FPUFlags?

In "Safe command prompt only" no AUTOEXEC.BAT of course, but standard PATH is loaded. I noticed after loading DOSKEY without switches, the typing mode is actually "overwrite". Typing <insert> changes the mode to "insert", and back. With switch /insert DOSKEY starts in insert mode - if prefered.

I use DOSKEY a lot, thanks for the links. To make it permanent, following line in AUTOEXEC.BAT is convenient: DOSKEY /insert Also as first command in "Safe command prompt only", /insert can be changed to /overwrite with "insert key".

Part VIII: Windows 98se on other USB 2.0 partition with Grub4Dos Memdrive bootchain It's possible to extend Part V to bootchain a full Windows installation on a logical drive with boot sector and “system”. All that has to be done is adding "uuid --write (hd0,0) "Volume serial number"" of the wanted Windows boot partition to MENU.LST (after "map --hook", no quotes). The Memdrive partition has same limits as Part V, but 400-500MB will be enough for the bootchain. The Windows boot partition will be limited only by the USB legacy BIOS (all my test machines can’t pass the 137GB/128G(i)B border while booting USB drives; IDE/SATA drives has no problems). If the Windows-directories are identical, the bootchain gave no troubles. During my testing the bootchain “worked” if at least all configuration files are identical and the Memdrive bootchain partition has all the system files needed until the Windows boot partition “takes over” (in BOOTLOG.TXT up to Init Success usbmphlp.pdr ). BTW: Changes made to critical files in the Windows-directory should be copied to the USB boot partition before next boot. These changed files can be “loaded” from “Command prompt only” after booting IO.SYS on the Memdrive (changes to real-mode drivers should be “implemented” earlier). BTW2: Bootchain is also possible with a Memdrive from other logical partition or virtual hard drive/image. The full Windows installation can be made on another primary drive too.

Part VII: Installation of Windows 98se on a logical partition with Grub4Dos Installation of Windows 98se on a logical drive gave me some troubles. After writing a boot sector and “system” to the logical partition in use with SYS D: (or other drive-letter), there where in-situ related installation problems with SCANDISK.EXE. With about 6-8 logical drives while the last one was hidden, all IO.SYS versions except RLoew´s PATCHPAR version, had problems accessing the primary usb boot drive as last in-situ drive. Installation from CD-ROM will install original IO.SYS and can give this problem with use of map --in-situ (hd0,4)+ (hd0). Although there are several workarounds, following MENU.LST will do the job: ------------------------------ MENU.LST ------------------------------ # comments before a command title Boot IO.SYS from first primary partition unhide (hd0,4) root (hd0,0) chainloader /io.sys title Install/boot IO.SYS from first logical drive for Win98se errorcheck off # no double access to first logical drive anymore hide (hd0,4) # shift (hd1) “up” if existing map (hd1) (hd) # shift usb boot drive “up” map (hd0) (hd1) # needed if floppy drive is in use. # after this mapping first “seen” by GRUB4DOS find-command map (fd0) (fd1) map (fd1) (fd0) # assuming first logical partition in-situ # one of four primary partition entries should be empty – else error 65 map --in-situ=1 (hd0,4)+1 (hd0) map --hook # experimental, after this mapping not “seen” anymore by “find” map (fd1) (fd0) map (fd0) (fd1) map --hook root (hd0,0) chainloader /io.sys ------------------------------ BTW: Most reliable Win98se setup will be SETUP /is /p i;s=detectbus,detectfloppy (because of HSFLOP.PDR incompatibility and possible Scandisk problems). For continuing the installation, see earlier parts. BTW2: The primary boot drive needs “system” only (SYS C:), together with GRUB.EXE and MENU.LST. The in-situ logical drive needs basic MSDOS 7.10 files. Easiest is copying the content of a WIN98SE bootdisk (without Ramdrive). This will give CD-ROM access too, if needed. BTW3: With in-situ Windows never detected a bootvirus ( https://jeffpar.github.io/kbarchive/kb/143/Q143281/ ). Otherwise see Part IV for a possible workaround.

I don't think you have to worry, you installed SP3 updates already. To be sure you can compare the content of BHDD31.ZIP with your files in WINDOWS, \SYSTEM, \COMMAND and \IOSUBSYS. if your files are older, just run _INSTALL.BAT (after unzipping BHDD21.ZIP to some directory).

@~♥Aiko♥Chan♥~ Still do not understand fully: has you old laptop a working hard drive (other than the 160GB you mentioned) and you want WinME clone to it from the USB flash drive?

@~♥Aiko♥Chan♥~ What exactly is your idea with WinME on that USB flash drive?

Good! Next step: go in Device Manager and disable ALL usb controllers. Without mouse: use TAB, arrow's and ALT+e to go to right places, and SPACE to enable/disable white square boxes (sorry, can't upload pictures, I have only 20KB upload space left...). Further if you want to disable SATA for the time being, set hard disk controllers to "None" (or something like that).

@~♥Aiko♥Chan♥~ When booting from an USB flash drive, is it possible to boot WinME in safe mode? Don't forget to set a MaxPhysPage line in SYSYEM.CB, say [386Enh] MaxPhysPage=20000.

To avoid possible misunderstandings, I found this for "map --in-situ=1 (hd0,4)+1 (hd0)" too. Today I repeated my experiments, I could reproduce anything EXCEPT "the original (hd0) is auto-mapped to (hd1), without change". I must have made some mistake. The in-situ (hd0) still have one partition, but the original (hd0) is fully "out/over-mapped" and needs to be mapped to be find again. For Part VI this has no consequenses, I prefer my setup; no need of more mapping and shifting of hard drives.

There should be one free partition entry, or "map --in-situ" gives me ALWAYS "error 65", with various combinations. This is not in the readme, but years ago already mentioned by tinybit. http://www.boot-land.net/forums/index_showtopic_11675.html And mentioned here too (not by tinybit this time). http://reboot.pro/topic/15167-how-to-boot-win9x-from-logical/ I just tried again some combinations with "(hd0,4)+1" and the third partition entry empty. With just "map --in-situ (hd0,4)+1 (hd0)" the logical partition becomes the first entry, the second and the fourth are unchanged. The original first entry becomes the third (the original free entry). Only with "map --in-situ=1 (hd0,4)+1 (hd0)" there is a standalone -mapped- (hd0,0), without other partitions. But the original (hd0) is auto-mapped to (hd1), without change. Mappings to (hd0,0) instead of (hd0) made no difference.

Part VI: Windows 98se from a logical partition on Grub4Dos Memdrive With a second, logical partition there are new possibilities. After writing a bootsector and “system” to the logical partition with SYS D: (or other drive letter), booting an existing Windows installation (copied to the logical partition) from the logical partition, or from a Memdrive is easy with following MENU.LST: ------------------------------ MENU.LST ------------------------------ # comments before a command title Boot IO.SYS from logical drive for Win98se errorcheck off # needed if floppy drive is in use map (fd0) (fd1) map (fd1) (fd0) # assuming one logical partition only # one of four primary partition entries should be empty map --in-situ (hd0,4)+1 (hd0) map --hook # experimental map (fd1) (fd0) map (fd0) (fd1) map --hook # map --rehook root (hd0,0) chainloader /io.sys title Windows 98se on Memdrive (from logical partition) with full USB 2.0 access # “usb --init” found incompatible with “map --in-situ” (experimental) # if GRUB.EXE is started without full reboot map --unhook usb --init errorcheck off map (fd0) (fd1) map (fd1) (fd0) map --mem (hd0,4)+1 (hd0) map --hook uuid --write (hd0,0) B00D-1D20 vol --write (hd0,0) U20MEMDRIVE map (fd1) (fd0) map (fd0) (fd1) map --hook # map --rehook root (hd0,0) chainloader /io.sys title Reboot IO.SYS on Memdrive uuid --write (hd0,0) B01D-1D20 vol --write (hd0,0) R20MEMDRIVE root (hd0,0) chainloader /io.sys ------------------------------ Further same as Part IV. A Part V bootchain is possible too, but USBCTLYS.REG will be imported exclusive from “Command prompt only” during an “in situ”-session; should be done before loading the Memdrive. Automation with batch-files is still possible, but for bootchain three batch-files will be needed. Part I, Part II and Part III installations are also possible (USB 1.1 legacy mode only). BTW: I found the use of “map --in-situ” incompatible with HSFLOP.PDR, tested on two machines (other two test-machines don’t have Floppy-controllers).

@tillewolle Realtek's Readme says DirectX8.1 minimum (WDM). You can try that version first.

@tillewolle Which version of DirectX is installed?

@tillewolle In case you want to test the win95 VXD-driver, search during updating the driver for /Win95/VALCX95.INF. If the Wizard has complaints, force updating. The inf-file doesn't specify a SUBSYS, but your VEN/DEV is mentioned.

Because of then Ven/Dev. If you google a bit, you will find lists like these: http://www.doc.ic.ac.uk/~svb/CS/Lab/Minix 3.1.0/drivers/libpci/pci_table.c Search in this list for 3059 only.

@tillewolle In the past I had a very resistant VIA-board. At last I succeeded with the 5.10.00.6240 driver from Biostar (my board was Asus!). A working download link is on this page: https://www.biostar.com.tw/app/en/mb/introduction.php/cpu_export.php?S_ID=5

@tillewolle At least you know an AC'97 driver is needed. On a MSI-forum about the same problem as yours, I found a link to A3.52 http://www.opendrivers.com/download/driver-11088.html Another idea on that forum was to try Win95 drivers.

@tillewolle The risks are all yours. I wold suggest this one, your hardware (C51G & ALC655) and your (main) VEN/DEV are mentioned. https://www.google.com/amp/s/www.driverguide.com/driver/amp/detail.php%3fdriverid=732403

@tillewolle Before starting with an experimental HDA-driver, you should be fully sure your board has a HD-audio codec (chip). If I search about sound for your motherboard, all I can find is ALC655. This appears to be an AC'97 codec. Did you try all Win98 drivers for this codec already?

@jaclaz Thanks for the tip. I tested the latest version of the program using Win98se and on two machines, with following results: 1) Can be used for Part I, Part III and Part V installations (no UUID changes in these parts!). A Reboot is always necessary. 2) Letter Assigner changes letters in MD-DOS already, assignments are found to be NOT compatible with SMARTDRV.EXE - Warning: Unable to use a disk cache on the specified drive (not mentioned in the HELP doc's). So speed gained for ALL drives in MS-DOS Compatibility mode, is lost by using Letter Assigner for assigned drives. This is less severe in Part V: the USB 2.0 drivers don't use Smartdrive; for some "Administrator" activities (starting Windows with USB-controllers disabled), the root partition in USB legacy mode is still cached by Smartdrive. 3) Letter Assigner checks for the Windows partition with UUID entrances in the file LETTERS.INI. In Part II and Part IV the UUID of the Memdrive is ALWAYS different from the UUID of the Windows partition on the USB boot drive. Since it's a goal of the project to have always access to this partition, the results with Letter Assigner are not compatible with starting Windows from a USB legacy drive after installation on a Memdrive; and the other way round. In the first case the C-drive will vanish after LETASSIG.EXE is started during execution of AUTOEXEC.BAT. In the second case I had a very, very bad crash while booting Windows on the Memdrive. It should be possible to replace LETTERS.INI-files before, but for sure this will not be easier than just calling SMARTDRV.EXE and SUBST.EXE in a batch file, with the right drive letters. 4) If the Windows volume is commented out in LETTERS.INI, assignment of other volumes is still working. The program gives only a message during execution of AUTOEXEC.BAT: Bad descriptor: ;;C=(1234-5678) Bad descriptor: ;;W=(8765-4321) Bad descriptor: ;;/WD=(8765-4321) The new volume mapping has been set up. Volume D was mapped without problems to X (except Smartdrive caching)! 5) Volumes on real USB 2.0 drives are changed roughly in the same way as Device Manager operates. Only in case of a non-removable USB drive, Letter Assigner is special. Using Device Manager the USB drive has first to be set as "Removable", to change drive letters. After first reboot the drive can be set back as non-removable, new drive letters will be still there, but a second reboot is needed first. With Letter Assigner there is just one reboot needed. In the Registry (in HKLM\ENUM\SCSI\..somedrive..\) only one line "UserDriveLetterAssignment"="XZ" is added, while "CurrentDriveLetterAssignment" is changed to ="XYZ" (if XYZ are new volume letters of an USB hard drive with three partitions). With Device Manager there will be three other lines in the Registry-entrance left, but they are only needed in case of a truly removable USB (flash) drive and do no harm otherwise (as far as I observed). 6) Labels changed, by Letter Assigner are NOT compatible with the GRUB4DOS "vol --write"-command.

Congratulations I have been reading our old thread, once you mentioned (page 7?) there was a difference according playback of system sounds after replacing one of my ALC883 specific HDAICOUT.HDA with a newer one.

Part V: Windows 98se on USB 2.0 with Grub4Dos Memdrive as bootchain If the MS-DOS “Volume Serial Number” of the Memdrive isn’t changed, Windows will boot further from the USB boot drive – partition with identical serial. The “outmapped” USB boot drive is invisible to IO.SYS while booting from the Memdrive, so not mounted in MS-DOS. If the Memdrive is (almost) identical to the USB boot partition, Windows doesn’t care. It´s really nice to see BOOTLOG.TXT, on the primary (boot) partition of the USB drive, starting with Init Success usbmphlp.pdr. Installation of USB-drivers should be finished before (see Part IV). In MENU.LST of Part IV only the UUID command has to be deleted (or commented out). “Rebooting” the Memdrive is only possible before starting Windows. BTW: “Reboot to MS-DOS mode” is impossible (Memdrive is not accessible anymore), no restarting Windows and no normal shutdown. "Restart" is the only option left, turning off the computer after a full reboot from ""Command prompt only". BTW2: USB 2.0 boot drive cannot be removed anymore. BTW3: Not all programs are working if Windows is on an USB drive with removable bit (no IOCTL ??). USB hard drives gave no problems. BTW4: On my hardware and with Grub4Dos the primary partition as Memdrive bootchain is max 3406MB (with minimum 16BM memory left for Windows 98se and 32MB for Grub4Dos!). On a SATA-II drive in an USB 2.0 caddy, my “best” load speed was 38MB/sec. (with “usb --init”). BTW5: This part can be combined with a logical partition. Desired fixed drive-letter should has been set one “higher” in Device Manager (logical partition “slips” one “down”). BTW6: For automation I start GRUB.EXE with a batch file after renaming HSFLOP.PDR and importing USBCTLYS.REG in the registry to enable the USB-drivers. To boot Windows from an USB legacy drive I use another batch file with “:USBLOGICAL1” (see Part IV), further CHOICE to load SMARTDRV.EXE for USBPRIMARY1 only, enable HSFLOP.PDR and disable USB-drivers by importing USBCTLNO.REG in the registry.