Rugxulo wrote: > Hi, > > On Wed, Mar 30, 2016 at 6:11 AM, matthew berardi > <matthewbera...@gmail.com> wrote: > >>let's assume UEFI+GPT is the problem, how do I fix it? >> >>I do usually boot UEFI > > > But I'm not sure that all so-called UEFI machines even offer CSM, so > you may be out of luck. > > https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#CSM_booting > > Though it could also be your particular USB key doesn't support > booting. (Some few don't, but most do.) You may wish to try an > entirely different jump drive. (Or are you only testing hard drives??) > > You could also try this guy's USB creation method: > http://joelinoff.com/blog/?p=431 > > If none of that works, you may be stuck with VMs. (But honestly, > that's not too horrible, they work pretty well these days, e.g. QEMU / > KVM, VBox, etc.) See here: > https://www.lazybrowndog.net/freedos/virtualbox/
Hello, Your problem could also be due to you are trying to boot from a hard disk when the used freedos image is done for a removable drive. So you have to edit the freedos image to change disk number in the boot sector (byte 36 of image shall be set from 0 to 128 considering you are using the first internal disk). The number of sectors per track and heads per cylinder will be wrong also. But I do not know if the boot sector and kernel code relies on them or automatically detects these parameters through int 0x13 (or use extended int 0x13 in which case they are meaningless). If it uses definitions from boot sector, you will have to update them either. Regards, Damien ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
