Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FDPP gets confused about boot drive #32

Closed
andrewbird opened this issue Oct 15, 2018 · 8 comments
Closed

FDPP gets confused about boot drive #32

andrewbird opened this issue Oct 15, 2018 · 8 comments

Comments

@andrewbird
Copy link
Member

Booting the same disk configuration under FreeDOS and FDPP gives different results. On FreeDOS the boot proceeds as expected, on FDPP it can't find the files referenced in config.sys or autoexec.bat itself.

FreeDOS 1.20

fd-120

FDPP from git

fdpp

I've attached the installation files
test-imagedir.tar.gz

Run from dosemu build directory as

bin/dosemu.bin -n -f test-imagedir/dosemu.conf -D+dRW -o test.log --Fimagedir test-imagedir

Firstly with your fdppkrnl.sys in test-imagedir/dXXXXs/c then replace that with kernel.sys from FreeDOS 1.20

@stsp
Copy link
Member

stsp commented Oct 15, 2018

How about using the full path to emufs.sys?

@andrewbird
Copy link
Member Author

Yes, but that's a symptom. It can't find autoexec.bat and lands on the D: drive afterwards.

@stsp
Copy link
Member

stsp commented Oct 15, 2018

Try fdconfig.sys instead of config.sys

@andrewbird
Copy link
Member Author

Yes renaming config.sys to fdconfig.sys worked, why?

@stsp
Copy link
Member

stsp commented Oct 15, 2018

The fdpp boot procedure differs a lot from
all other boot procedures.
dosemu2 looks for different files for fdpp
(fdconfig.sys, command.com), and points fdpp
to them. So the bug is not here, but in dosemu2.
I'll look at what happens.

@stsp
Copy link
Member

stsp commented Oct 15, 2018

This is now fixed.
The problem was the presence of a hdimage,
for which I assumed the presence of all needed
files (because of the inability to look inside).
If that hurts, I stopped doing so.

@stsp stsp closed this as completed Oct 15, 2018
@andrewbird
Copy link
Member Author

That's looking a lot better thanks

Test PP-DOS-1.00 FAT12 image file ... SKIP: Booting from image not supported
Test PP-DOS-1.00 FAT12 image file D writable ... ok
Test PP-DOS-1.00 FAT12 vfs directory ... ok
Test PP-DOS-1.00 FAT12 vfs directory boot.blk ... SKIP: Not supported by Boot Block
Test PP-DOS-1.00 FAT16 image file ... SKIP: Booting from image not supported
Test PP-DOS-1.00 FAT16 image file D writable ... ok
Test PP-DOS-1.00 FAT16 vfs directory ... ok
Test PP-DOS-1.00 FAT16 vfs directory boot.blk ... SKIP: Not supported by Boot Block
Test PP-DOS-1.00 FAT16B image file ... SKIP: Booting from image not supported
Test PP-DOS-1.00 FAT16B vfs directory ... ok
Test PP-DOS-1.00 FAT16B vfs directory boot.blk ... SKIP: Not supported by Boot Block
Test PP-DOS-1.00 FAT32 disk info ... ok
Test PP-DOS-1.00 FAT AUTO vfs directory ... ok
Test PP-DOS-1.00 Floppy image file ... SKIP: Booting from image not supported
Test PP-DOS-1.00 Floppy vfs directory ... ok
Test PP-DOS-1.00 INT21 disk info ... ok
Test PP-DOS-1.00 LFN volume info on FAT(img) ... ok
Test PP-DOS-1.00 LFN volume info on MFS ... ok
Test PP-DOS-1.00 MFS auto hd vfs directory redirection ... ok

@stsp
Copy link
Member

stsp commented Oct 15, 2018

Thanks for taking care of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants