Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

WDe and GPT, booting DOS (Users)

posted by Richard, 22.11.2022, 07:10

>
> There are ( at least ) 2 possibilities: "grub-mkconfig" or "update-grub".
> The latter is better because it doesn't need any arguments. Must be run as
> root, though: "sudo update-grub".
>
> If everything's ok, that program should finally display something like
> "found DOS/Win31 partition on /dev/sdd'.




Nothing seems to work for me.


After a few re-installs on both INTEL and AMD Computers - the GNU GRUB version 2.06 menu looks like

Linux Mint 21 Cinnamon
Advanced options for Linux Mint 21 Cinnamon
FreeDOS (on /dev/sda2)
FreeDOS (on /dev/sda3)
UEFI Firmware Settings


Note that in above Menu - the "FreeDOS" is actually MSDOS71 - there is something about the MSDOS71.iso I have used to create MSDOS71 - there is actually reference to FreeDOS.


/dev/sda2 is actually the original MBR version of MSDOS71
/dev/sda3 is actually the Japheth GPT modifications of MSDOS71


When I select /dev/sda3 from the Menu I get the error


error: can't find command 'drivemap'
error: invalid EFI file path



Alternatively. if I via the GRUB Menu above, do
*UEFI Firmware Settings
F9 Boot Device Options
Notebook Hard Drive

in a DOS screen I get

A> type the name of the command interpreter (e.g. C:\Windows\command.com)

and no matter what I try e.g.

A> c:\command.com
A> d:\command.com
A> e:\command.com

etc

it just returns me to the prompt

A> type the name of the command interpreter...




Note that

In Windows 10, I used a Partition Assistant to copy the partition of the modified to GPT MSDOS71 - from the MBR partition style hard drive where the MSDOS71 (MBR) and MSDOS71 (GPT) were located - to a GPT partition style hard drive where Linux and Windows 10 also reside.

With my very limited knowledge of MBR and GPT - I guess that to use the GPT style MSDOS71, it would have to be located on a GPT style hard drive.

I could not locate genuine MSDOS71 to install - so I downloaded from way-back machine a MSDOS71 iso (which during installation makes mention of FreeDOS).

My computers date from about 2014 and onwards - my best computer has 3 BIOS settings

Legacy
CSM + UEFI
UEFI only

and for some reason LINUX + Windows only wants to work with UEFI only on a GPT Partition Style drive (in my case 4 TB) - I ensured that approx 500 MB partitions were within the first 2 TB for the MSDOS71 GPT.






For anyone who has tried the modifications for GPT (e.g. Japheth et al) - I assume the GPT version works for you - could you give some guidance on what I did wrong (e.g. not genuine MSDOS71, hardware too new, hard drive partition style incorrectly set, etc)?


Windows 10 "sees" both MBR and GPT versions of MSDOS71 (e.g. Explore in Disk Management) when these are on GPT Partition style Hard drive. MSDOS71 Fdisk seems to have trouble assigning the active partition when changing from MBR<->GPT version of MSDOS71 (being on a MBR Partition style hard drive).


Is it fair to say that the intention of the modification was to allow BOOTING of MSDOS71 from a GPT partition (rather than the GPT partition being only a Data Partition)?


If I understand the significance of WDe correctly -

It is a tool that can save to a file, a whole (or part thereof) partition.


The best I previously had to date was a partition assistant tool which CLONES a partition (i.e. does not generate a file).


WDe I think only works with drives (C D E etc) - any chance to let it explore any partition that is NOT a drive?

 

Complete thread:

Back to the forum
Board view  Mix view
22049 Postings in 2034 Threads, 396 registered users, 142 users online (0 registered, 142 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum