6/28/2021 0 Comments Grub4Dos 1.1
Deleting volume-label with LABEL.EXE erased both, and the directory-entries were overwritten after copying files to the drive.
Grub4Dos 1.1 Software Or SetPlease disable ad-blocking software or set an exception for MSFN.Alternatively, register and become a site sponsorsubscriber and ads will be disabled automatically.Two parts are about the Windows 98 Second Edition installation using the legacy USB-connection.All installations are possible in directory C:WINDOWS: no drive-letter assignment needed. In retrospective everything is easygoing, although later parts and project extensions are more complicated. Except Grub4dos, everything is experimental and (almost) undocumented. ![]() Loew). With my fastest USB-drive BOOTLOG.TXT gives 6 seconds boot-time. Grub4Dos 1.1 Drivers And VcacheMemdrive will be max 400-500MB, mainly depending on drivers and vcache. I used vcache MinFileCache1024 and MaxFileCache1024 during experimenting. GRUB.EXE (0.4.6.a) can be started from real MS-DOS with following MEN U.LST. A logical partition can get a fixed drive-letter with SUBST, but the drive-letter will shift if booting from the Memdrive. SUBST for different drive-letters can be automated with following batch-file, USB11.BAT. The command didnt work anymore for renaming a Drivespace Host-drive, and too when I formatted an USB-drive with FORMAT. Same story with LABEL.EXE. If the label is deleted by LABEL.EXE, the vol --write-command is working again. In PTEDIT.EXE can be seen that the vol --write-command is not writing to the FAT, while LABEL does. Also labels written by Mini-Tool-Partition Magic and RMPREPUSB I found not compatible with the vol --write-command of Grub4Dos. ![]() With the first two mappings Drive-letters are reversed, with last two mappings everything is back to nomal. My built-in Floppie-station is now always A: and an attached USB-FDD always B: Hard-drives gave no problems after booting the Memdrive. With cat --hex (hd0)01 not, but with cat --hex (hd0,0)01 too. If I write vol --write (hd0,0) VOLGRUBOKE (or with (fd0)), VOL is displaying this happily in MS-DOS, but the bootsector is still NO NAME. If try to write the same volume name with LABEL.EXE, the -character is refused, luckily VOLGRUBOKE is accepted. The volume-label was further written to the Bootrecord in Sector 0 and to the Backup-bootrecord in sector 6. Changing volume-label in Bootsector after erasing in Directory was useless, no output from MS-DOS 7.1 VOL, DIR, LABEL.EXE and FDISK.EXE anymore. Writing volume-label with vol --write (hd0,0) GRUBDOSNAME gave this volume-label as second Directory-entry only, with attributes - - - - V and as date 0-00-80 (whole entry is marked RED by Diskedit, but okay after writing a valid date). Grub4Dos showed this label as sRUBDOSNAME (Greek s, cant show it in this post) and was willing to write a new volume-label.
0 Comments
Leave a Reply. |