deomsh

In case of VBEMP9x you can try DirextX software emulation enabling Direct Draw and possibly Direct 3D (results depends on system speed). See: http://www.mdgx.com/newtip18.htm

I needed an empty Memdrive, accessable by MS-DOS and by Grub4Dos. While using an empty gzipped DosBox image, sometimes the Memdrive was "ready", sometimes had to be formatted first in MS-DOS. They make no sense whatsoever. 1) you map an existing (compressed) image residing on floppy to current hard disk (which may be *whatever* depending on what has been run before and on the setup) and the result could be anything (and the contary of it) depending on the contents of the image 2) you hook the mapping 3) you set root to the floppy 4) you chainload the OS file on floppy In those the image is simply mapped and is not changed by any of the commands you listed, and BTW you never access it from grub4dos. There is no bootsector in the uncompressed image as far I can judge (which is not so far) Further: I have no need to access the content of the image from Grub4Dos. All right, here they are. For convenience I added parttype (hd-1,0). USB-FDD; first set of commands(no HDD’s attached; one real Floppy) map --mem --heads=0 --sectors-per-track=0 (fd0)/hdd-512mb.img.gz (hd) Autodetect number-of-heads failed. Use default value 255 Autodetect sectors-per-track failed. Use default value 63 [xxxM/511M] floppies_orig=2, harddrives_orig=0, floppies_curr=1, harddrives_curr=1 map --hook parttype (hd-1,0) Partition type for (hd0,0) is 0x0E. root (fd0) Filesystem type is fat16, using whole disk Volume Name is “USBFDSILVER”. chainloader /io.sys Will boot MS-DOS 7.x from drive=0x0, partition=0xff(hidden sectors=0x0) boot Memdrive accessed with MS-DOS 7.1: A:\ >VOL C: gives (Dutch!): Het mediumtype is ongeldig. Bezig met lezen station C Afbreken, Opnieuw proberen, Mislukt (same as “Invalid mediatype” and “Abort/Retry/Fail”) The Memdrive need to be formatted. Bootsector is filled out in a way unknown to me (as shown by PTEDIT). USB-FDD; second set of commands map --mem --heads=0 --sectors-per-track=0 (fd0)/hdd-512mb.img.gz (hd) Autodetect number-of-heads failed. Use default value 255 Autodetect sectors-per-track failed. Use default value 63 [xxxM/511M] floppies_orig=2, harddrives_orig=0, floppies_curr=1, harddrives_curr=1 map --hook parttype (hd-1,0) Partition type for (hd0,0) is 0x0E. insmod fat fat loaded fat mkfs (hd-1,0) FAT subtype: FAT16 Sectors per cluster: 32 Sectors per FAT:128 Number of free clusters: 32755 Total clusters: 32755 FAT start sector: 1 524080 KB total drive space. 524080 KB available. root (fd0) Filesystem type is fat16, using whole disk Volume Name is “USBFDSILVER”. chainloader /io.sys Will boot MS-DOS 7.x from drive=0x0, partition=0xff(hidden sectors=0x0) Memdrive accessed with MS-DOS 7.1: A:\>VOL C: gives normal output Bootsector is like described in my post of https://msfn.org/board/topic/180597-exploring-setup-p-isdetectbus-and-grub4dos-8½-times-win98se-on-usb-drive/?do=findComment&comment=1176826 (Scandisk did found errors). USB-FDD; third set of commands insmod fat fat loaded map --mem --heads=0 --sectors-per-track=0 (fd0)/hdd-512mb.img.gz (hd) Autodetect number-of-heads failed. Use default value 255 Autodetect sectors-per-track failed. Use default value 63 [xxxM/511M] floppies_orig=2, harddrives_orig=0, floppies_curr=1, harddrives_curr=1 map --hook parttype (hd-1,0) Partition type for (hd0,0) is 0x06. root (fd0) Filesystem type is fat16, using whole disk Volume Name is “USBFDSILVER”. chainloader /io.sys Will boot MS-DOS 7.x from drive=0x0, partition=0xff(hidden sectors=0x0) Memdrive accessed with MS-DOS 7.1: >A:\VOL C: gives normal output Bootsector is “normal” (mediatype: F8), Scandisk didn’t found errors. USB-FDD; fourth set of commands insmod fat fat loaded map --mem --heads=0 --sectors-per-track=0 (fd0)/hdd-512mb.img.gz (hd) Autodetect number-of-heads failed. Use default value 255 Autodetect sectors-per-track failed. Use default value 63 [xxxM/511M] floppies_orig=2, harddrives_orig=0, floppies_curr=1, harddrives_curr=1 map --hook parttype (hd-1,0) Partition type for (hd0,0) is 0x06. fat mkfs (hd-1,0) FAT subtype: FAT16 Sectors per cluster: 32 Sectors per FAT:128 Number of free clusters: 32755 Total clusters: 32755 FAT start sector: 1 524080 KB total drive space. 524080 KB available. root (fd0) Filesystem type is fat16, using whole disk Volume Name is “USBFDSILVER”. chainloader /io.sys Will boot MS-DOS 7.x from drive=0x0, partition=0xff(hidden sectors=0x0) Memdrive accessed with MS-DOS 7.1: A:\>VOL C: gives normal output Bootsector is NOT “normal” (mediatype: F0) Scandisk did found errors as described earlier. USB-FDD; fifth set of commands root (fd0) Filesystem type is fat16, using whole disk Volume Name is “USBFDSILVER”. map --mem --heads=0 --sectors-per-track=0 (fd0)/hdd-512mb.img.gz (hd) Autodetect number-of-heads failed. Use default value 255 Autodetect sectors-per-track failed. Use default value 63 [xxxM/511M] floppies_orig=2, harddrives_orig=0, floppies_curr=1, harddrives_curr=1 map --hook parttype (hd-1,0) Partition type for (hd0,0) is 0x06. chainloader /io.sys Will boot MS-DOS 7.x from drive=0x0, partition=0xff(hidden sectors=0x0) Memdrive accessed by MS-DOS 7.1: >A:\VOL C: gives normal output Bootsector is “normal”, (mediatype: F8). Scandisk didn’t found errors. It appears that if an USB-FDD is used, I solved my problem giving the command root (fd0) before map --mem. In case of USB-HDD the first set of commands above is enough to obtain an empty Memdrive, ready for the next steps of Part 8½ of my project.

I do not understand "i use the SSD program...". Which video card is in use?

Maybe Exlor98 is worth trying. https://msfn.org/board/topic/84886-the-complete-list-of-hotfixes-updates-for-windows-98se/

I used following commands: title Map hdd-512mb.img.gz and boot USB-FDD # BEFORE # insmod fat map --mem --heads=0 --sectors-per-track=0 (fd0)/hdd-512mb.img.gz (hd) map --hook # AFTER # insmod fat # fat mkfs (hd0,0) root (fd0) chainloader /io.sys I experimented further with four different USB-FDD's and a handfull of USB-HDD´s. The results I described earlier where only existent on USB-FDD's and only if the image was located on an USB-FDD too. On USB-HDD Grub4Dos made out of all empty DosBox images perfect Memdrives. With Partition ID 06, OEM ID MSDOS5.0 and standard FAT16 formatting (Diskedit, Scandisk and SETUP gave no errors). At last I found that in case of USB-FDD setting root (fd0) BEFORE the map-commands had exactly the same effects as sole insmod fat, so the FAT module doesn't seem to be needed in Part 8½ of my project. Same as "Sectors per FAT" (as a layman I have to rely on authority, I use Scott Mueller's Repairing and Upgrading PC's for my terminology). I will have to study these things first more carefully. I will go mainly for FAT16 - because of map --mem my USB-FDD's. Thanks a lot for all info.

@jaclaz Thanks a lot, I had some interesting hours with Grub4Dos, again. I didn't knew this module exists, only found that Grub4Dos wasn't able to format a drive. I did many tests with insmod fat and fat mkfs on an empty "Part 8½ Memdrive", with following results: The Memdrive was formatted directly. insmod fat-command given BEFORE map --mem forced Partition ID 06 and (other CHS values than without). If given AFTER, Partition ID remained to 0E. Scandisk complained about the Mediabyte and missing Second FAT, but could repair them. Win98se SETUP gave a SU-0013 error (saw this one never before). SETUP continued if system was transferred to the Memdrive first with SYS C: (wasn't needed in case of Part 8½: USB-FDD). Diskedit saw an error in the Mediabyte too. About the Bootsector: BPB_SecPerClus and BPB_FATSz16 where different from what "DOS expects". Further was BPB_HiddSec zero. BPB_Media was F0h (instead of F8h). So far the bad news. The good news: during experimenting I "discovered" that giving the command insmod fat BEFORE map --mem, and commenting out fat mkfs, resulted in a fully formatted FAT16 Memdrive with Partition ID 06 and a valid bootsector (from an empty image file)! Gimme such a tool for FAT32 too... I am becoming more interested in your Catedit batch, because of my need to RESIZE the Memdrive in case of mapping a whole USB-FDD to a Memdrive (USB-FDD with saved Windows installation from Part 8½). I bought two 512MB USB drives at AliExpress, incredible how cheap they are. Although seeming only different in color, they appeared to be much more different. One was effective 480MB, the other 502MB. Good with VBEMP 32MB as video driver, but a little to big with Windows' standard VGA or with the NVidia driver for my card. Better would be 400-420MB. Is there any chance your script could be of help in this matter?

Part 8½: Full installation of Windows 98se on a Grub4Dos Memdrive This part is maybe a bit off-topic, but a possibility to use an USB-FDD. Especially older machines cannot boot from USB-HDD. It even turned out possible to use one 1.44MB floppy disk only - together with the Windows 98se CD-ROM! The idea is to make an empty Memdrive with Grub4Dos by mapping an empty image file to memory (with gz-compression only 500-615 KB), and then boot the legacy USB drive first. From MS-DOS 7.1 “Command prompt only” the Memdrive can be formatted, unless the image file is formatted already. Only if installing from USB-HDD, the “System” has to be transferred with SYS [Drive letter]: and some (bootdisk) MS-DOS 7.1 files has to be copied to the Memdrive (in that stage NOT C:). These steps are simple. More difficult is to omit the Windows’ SETUP Reboots. Omitting the first reboot after SETUP dialogues and copying files is almost undocumented (see: http://rjnoe.home.xs4all.nl/0/pc/soft/win/setup/msbt95a.txt ), but turned out to be very easy: adding “Reboot=0” to MSBATCH.INF [Setup] (no quotes). After copying files SETUP stopped, showing the MS-DOS command-prompt started from. To omit reboots during following phases of SETUP, I patched RUNONCE.EXE. I found the idea of patching this file in an old MSFN-tread about “Windows 98 Live-CD Project”, but nowhere a “how-to”. By trial and error and studying Windows’ Reboot and Restart commands, I succeeded at last (a HEX-editor is needed). With patched RUNONCE.EXE Windows can be restarted with “RUN » RUNONCE –q” (no quotes). After installation of Windows 98se directly on the Memdrive, Part 8½ is identical to Part II or Part IV. Further installation can be continued in the same ways, but only as long as the Memdrive exists. Other possibilities are: - Saving to a small, bootable USB-FDD. Later loading the USB-FDD and mapping the Memdrive to first HDD. - Saving with WinImage 8.1 (shareware) to an image WITHOUT Master Boot Record on a bootable USB drive/partition of choice. The image file has to be loaded and mapped to first HDD (hd0). --------------------------------------------------------------------------------- PATCH RUNONCE.EXE ------------------------------ Instead of: “rundll.exe setupx.dll,SxShowRebootDlg_RunDll 15” use “rundll.exe user.exe,exitwindowsexec ”. In HEX, replace: “73 65 74 75 70 78 2E 64 6C 6C 2C 53 78 53 68 6F 77 52 65 62 6F 6F 74 44 6C 67 5F 52 75 6E 44 6C 6C 20 31 35” with: “75 73 65 72 2E 65 78 65 2C 65 78 69 74 77 69 6E 64 6F 77 73 65 78 65 63 00 00 00 00 00 00 00 00 00 00 00 00” --------------------------------------------------------------------------------- I used following MENU.LST, two versions: one in case of USB-FDD and one in case of USB-HDD. --------------------------------------------------------------------------------- MENU.LST ------------------------------ # USB-FDD/ Floppie version # comments before a command title Chainload IO.SYS from USB-FDD root (fd0) chainloader /io.sys title Commandline commandline title Make empty Memdrive with Legacy USB 1.1 access - boot USB-FDD map (hd0) (hd) # some empty IMG files do not need formatting afterwards # FAT16 map --mem --heads=0 --sectors-per-track=0 (fd0)/hdd512im.gz (hd0) # FAT32 # map --mem --heads=0 --sectors-per-track=0 (fd0)/32hd420M.img.gz (hd0) map --hook # working if formatting wasn’t needed vol --write (hd0,0) SETUPMEMDRV root (fd0) chainloader /io.sys title Boot IO.SYS with HIMEMX on Memdrive map (fd1) (fd0) map (fd0) (fd1) map --hook vol --write (hd0,0) MEMDRIVE982 root (hd0,0) chainloader /io.sys pause Remove USB drive title Map USB-FDD and boot IO.SYS on Memdrive # do not use usb --init if Windows hasn’t USB drivers # if in use add mbrint13.sys to IOS.INI [SafeList] # usb --init map (hd0) (hd) # first test from commandline to find C/H/S: map --mem (fd0)+1 (hd0) map --mem --heads=64 --sectors-per-track=32 (fd0)+1 (hd0) map --hook map (fd1) (fd0) map (fd0) (fd1) map --hook map --floppies=2 uuid --write (hd0,0) 1234-5678 vol --write (hd0,0) MEMDRIVE982 root (hd0,0) chainloader /io.sys # no need to remove USB drive title Map Win98se Image and boot IO.SYS on Memdrive errorcheck off map (hd0) (hd) map --mem (fd0)/MEMDRV98.IMA (hd0) map --hook map (fd1) (fd0) map (fd0) (fd1) map --hook uuid --write (hd0,0) 1234-5678 vol --write (hd0,0) MEMDRIVE982 map --floppies=2 root (hd0) chainloader /io.sys title Reboot IO.SYS on Memdrive root (hd0,0) chainloader /io.sys --------------------------------------------------------------------------------- The USB-FDD has to be booted with HIMEM.SYS (!). After making and formatting the Memdrive (if still needed), and after copying at least HIMEMX.EXE, GRUB.EXE and MENU.LST to the empty Memdrive, a full Windows’ installation can be started directly with: “SETUP [Drive][Path]MSBATCH.INF /ir /is /nf /nr /IW /p i;s=detectfloppy” (no quotes). For a quasi-universal installation: “SETUP [Drive][Path]MSBATCH.INF /ir /is /nf /nr /IW /p i;s =detectbus,detectfloppy”. First five setup switches mentioned are most safe and convenient, not mandatory. If a Windows 98 installation exists on an attached hard disk, installation in a directory with another name is mandatory – otherwise there is a high risk the configuration of the existing Windows installation will be used by SETUP. If SETUP has finished the “copy files” part, IO.SYS on the the Memdrive has to be booted from the command-prompt with Grub4Dos, while using HIMEMX.EXE. Afterwards patched RUNONCE.EXE has to be copied to C:\%winbootdir%\SYSTEM. Other desired changes can be made too. After giving the WIN-command, SETUP will continue. I found my patched RUNONCE.EXE restarted Windows twice, installing Windows further in the usual way - up to the Welcome screen. --------------------------------------------------------------------------------- MENU.LST ------------------------------ # USB-HDD version # comments before a command title Chainload IO.SYS from USB-HDD root (hd0,0) chainloader /io.sys title Commandline commandline title Make empty Memdrive with Legacy USB 1.1 access - boot USB-HDD # some empty IMG files do not need formatting afterwards # FAT16; about 500MB map --mem --heads=0 --sectors-per-track=0 (hd0,0)/hdd-512mb.img.gz (hd) # FAT32; about 420MB # map --mem --heads=0 --sectors-per-track=0 (hd0,0)/32hd420M.img.gz (hd) map --hook map (fd1) (fd0) map (fd0) (fd1) map --hook # working if formatting not needed vol --write (hd-1,0) EMPTYMEMDRV root (hd0,0) chainloader /io.sys title First boot IO.SYS on Memdrive (with HIMEM.SYS) map (hd0) (hd-1) map (hd-1) (hd0) map --hook vol --write (hd0,0) SETUPMEMDRV root (hd0,0) chainloader /io.sys title First reboot of IO.SYS on Memdrive (with HIMEMX.EXE) vol --write (hd0,0) MEMDRIVE982 root (hd0,0) chainloader /io.sys pause Remove USB drive title Reboot IO.SYS on Memdrive root (hd0,0) chainloader /io.sys ------------------------------------------------------------------------------------ After booting the USB-HDD, making the empty Memdrive, formatting and installation of basic MS-DOS 7.1 on the empty Memdrive, IO.SYS on the Memdrive has to be booted with HIMEM.SYS (!). CONFIG.SYS or AUTOEXEC.BAT is not needed, only copying MSDOS.SYS (like the one below – attributes SHR), HIMEM.SYS, DBLBUFF.SYS, GRUB.EXE and MENU.LST to the root. Same in case of other real mode drivers needed. IO.SYS will load HIMEM.SYS and DBLBUFF.SYS by default, messages about IFSHLP.SYS and WIN.COM can be ignored. Afterwards the Memdrive is the root-drive (C:). This time a full Windows’ installation can be started, further same as USB-FDD. ------------------------------------------------------------------------------------ MSDOS.SYS ------------------------------ ;SYS [Paths] WinDir=C:\ WinBootDir=C:\ HostWinBootDrv=C [Options] SystemReg=0 ; ;The following lines are required for compatibility with other programs. ;Do not remove them (MSDOS.SYS needs to be >1024 bytes). ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxb ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxf ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxg ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxh ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxi ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxk ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxl ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxm ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxn ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxo ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxp ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxq ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxr ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxs ------------------------------------------------------------------------------------ BTW: About empty images: FAT16 512MB images are readily available on the web. Following is *somehow* already formatted: http://sites.google.com/site/dotalshoff/games/dosbox With SplImgCreator.exe (Win9X compatible) unformatted FAT32 images can be created of each desired size, I used 420MB. See: http://reboot.pro/topic/15951-easy-creating-new-empty-img Compression to Grub4Dos-compatible gz-compression with 7-Zip. BTW2: If the Memdrive is readily available as C-drive, a Windows installation directly from CD-ROM is possible. Both the USB drive and the Memdrive should each time be booted with MS-DOS CD-ROM drivers. During ALL phases, SETUP must have access to the CD-ROM to avoid a full reboot (*somehow* different from USB-FDD/HDD, these can be removed before continuing setup). BTW3: Windows 98se on a Memdrive can be used together with R. Loew’s 32-bit and/or 64-bit Ramdrive(s) for more space. I set the Swapfile to a 2GB Ramdrive with the 32-bit RAMDISK and used the remaining memory for another Ramdrive with the 64-bit RAMDISK. BTW4: Following – annotated - MSBATCH.INF makes also mandatory or optional/ desired changes to MSDOS.SYS, CONFIG.SYS, AUTOEXEC.BAT and SYSTEM.INI. According to Q188101 it’s only possible to write twelve characters for filename using DevAddDev in MSBATCH.INF – no Drive/ Path, so files must reside in the Root. See: http://www.c-bit.net/Q188101/DE-DE (not found in English). Same turned out to be true for CmdAdd, but files can be in Path too. --------------------------------------------------------------------------------- MSBATCH.INF ------------------------------ ;; MSBATCH.INF ;; ;; Copyright (c) 1995-1999 Microsoft Corporation. ;; All rights reserved. ;; ;; Comments always BEFORE a command [BatchSetup] Version=3.0 (32-bit) SaveDate=01/15/20 [Version] Signature = "$CHICAGO$" [Setup] Reboot=0 ;; Never set System=0, MBR=0 or CleanBoot=1 [Install] UpdateInis=Edit.Sysini,Edit.Dossys UpdateCfgSys=Edit.Cfgsys UpdateAutoBat=Edit.Autobat [Edit.Sysini] ;; Mandatory - unless other methods are used %10%\system.ini,386Enh,,"MaxPhysPage=40000" ;; Optional ;; Convenient while copying whole Memdrive %10%\system.ini,386Enh,,"PagingDrive=C" ;; If using R. Loew’s RAMDISK ;;%10%\system.ini,386Enh,,"PagingDrive=S" ;; Watch free space on Memdrive %10%\system.ini,386Enh,,"ConservativeSwapfileUsage=1" %10%\system.ini,386Enh,,"DMABufferSize=64" ;; Watch use of System Arena ;; If MaxFileCache is below 1/24 of MEM, MinFileCache is mandatory %10%\system.ini,vcache,,"MinFileCache=1024" %10%\system.ini,vcache,,"MaxFileCache=1024" ;; If using R. Loew’s RAMDISK (simple method) ;;%10%\system.ini,386Enh,,"device=prothook.VXD" [Edit.Dossys] ;; Optional but convenient %30%\msdos.sys,Options,,"BootMenu=1" %30%\msdos.sys,Options,,"BootMenuDefault=5" %30%\msdos.sys,Options,,"BootMenuDelay=30" %30%\msdos.sys,Options,,"SystemReg=0" %30%\msdos.sys,Options,,"Logo=0" [Edit.Cfgsys] ;; Mandatory DevAddDev=HIMEMX.EXE,device,, ;; If using R. Loew’s RAMDISK ;;DevAddDev=HIMEMEX.SYS,device,, ;; One of both drivers needed in case of CD-ROM install ;;DevAddDev=XDVD2.SYS,device,,"/D:MSCD001" ;; Watch conventional memory! ;;DevAddDev=OAKCDROM.SYS,device,,"/D:MSCD001" [Edit.Autobat] ;; Optional, very convenient CmdAdd=doskey.com,"/insert" ;; One of both CD extensions needed in case of CD-ROM install ;;CmdAdd=Shcdx33f.com,"/D:MSCD001 /L:U /~+" ;; Optional CmdAdd=SMARTDRV.exe,"/X C+ /B:57344 /V" ;; Grub needs enough conventional memory - smaller Smartdrive Read-Ahead buffer! ;;CmdAdd=mscdex.exe,"/D:MSCD001 /L:U /M:20" ;;CmdAdd=SMARTDRV.exe,"/X C+ /B:32768 /V" ;; If using R. Loew’s RAMDISK ;;CmdAdd=ramdsk32.com,"S: 2097152" ;;CmdAdd=ramdsk64.com,"T:" ;; Inf,Reg and BAT files need always a Carriage Return on the end! Thank you, LoneCrusader! ;; Better use two semi-colons if using Windows 10 Notepad ---------------------------------------------------------------------------------

@~♥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.