Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

29 Excellent

About deomsh

  • Rank

Profile Information

  • OS
  • Country

Recent Profile Visitors

2,489 profile views
  1. @~♥Aiko♥Chan♥~ Did you try Gom player It's listed for win95 (didn't test it).
  2. Missed this post. Please can you explain ADIXctlLevel, ConservativeSwapFileUsage and FPUFlags?
  3. 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.
  4. 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".
  5. 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.
  6. 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.
  7. 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).
  8. @~♥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?
  9. @~♥Aiko♥Chan♥~ What exactly is your idea with WinME on that USB flash drive?
  10. 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).
  11. @~♥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.
  12. 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.
  13. 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.
  14. 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).
  15. @tillewolle Realtek's Readme says DirectX8.1 minimum (WDM). You can try that version first.
  • Create New...