VOGONS


First post, by danielc

User metadata
Rank Member
Rank
Member

Just wondering if this is a known issue or i'm doing something wrong. Here's what I did...

(01) Created the image with bximage.exe:
bximage -hd -mode=flat -size=8 -q DOOM1SW.IMG

(02) Mount it...
IMGMOUNT 2 Y:\IMG\DOOM1SW.IMG -SIZE 512,63,16,16 -T hdd -FS none
...then create a partition with FDISK and format it (as FAT16 of course)

(03) Restart DOSBox, mount it...
IMGMOUNT D Y:\IMG\DOOM1SW.IMG -SIZE 512,63,16,16 -T hdd -FS fat16
...and copy all my files over.

After running D:\DOOM1\DOOM.EXE, it takes about 8 seconds to load (versus 2 seconds for a mounted folder), and about TWENTY seconds to load the first level after choosing difficulty (versus 3 seconds for mounted folder).

Version is DOSBox v0.72 Win32 running under Vista x64. Config: CPU is dynamic/max and RAM is 8MB, all other stuff at defaults.

P.S. If anyone is planning to tell me to "use MOUNT to a folder instead", this is not a solution for me as I need to use images. Doom1 shareware was just a test (I use Doom Legacy to benchmark my DOSBox environment), I plan to have a copy of FreeDOS or 4DOS or something on there (undecided).

So I was just wondering if this is expected i.e. if anyone else experiences this, or have I done something wrong... any advice or suggestions are greatly appreciated =)

Last edited by danielc on 2009-03-12, 14:46. Edited 1 time in total.

Regards,
CosmicDan

Reply 1 of 10, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

this is not a solution for me as I need to use images.

Bad luck then, that's not how it's supposed to be used.

Reply 2 of 10, by danielc

User metadata
Rank Member
Rank
Member

Hmm ok. I understand that one of the dev's had to actually write the code for tha FAT filesystem in DOSBox yeah? So i guess the reason is because it's just not optimized or whatever.

So short answer - deal with it? 😀

...would loading SMARTDRV.EXE make any difference? Or, actually booting FreeDOS? Eh that was a rhetorical question i'll just try them anyway and fiddle around a bit, i'll be sure to post back if I get any interesting results. Cheers.

EDIT: Come to think of it, considering DOSBox emulates a ~486 computer, the loading times for Doom Legacy (it's the most fancy DOS sourceport of Doom FYI) seem pretty realistic. I don't have a real 486 to test, but from memory it seems about right...

Regards,
CosmicDan

Reply 3 of 10, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

First thing would be to write WHY you can't use local drives.

About the rest you're correct, nobody cares about the speed of the mounted
fat drive in a non-booted environment, it's used to transfer files nothing more.
Once you boot into msdos/freedos/whatever it's as fast as the respective dos
version is.

Reply 4 of 10, by danielc

User metadata
Rank Member
Rank
Member
wd wrote:

Once you boot into msdos/freedos/whatever it's as fast as the respective dos version is.

Fair enough - that's something I can live with.

wd wrote:

First thing would be to write WHY you can't use local drives.

I have started working on the PSP port of DOSBox by CrazyC, and the PSP's filesystem driver has a hardlimit of 8 or so simultaneous open handles to files on the MSDuo - it's the main thing holding back the game compatibility (crashes with missing file error, sometimes an overflow in the PSP kernel - early versions even corrupted the MemoryStick filesystem). Also, any game that needs DPMI swapping just dies - Doom Legacy being one of them - as soon as the app requesting protected mode is entered it just spits out memory addressing errors.

Anywho, my point is I have found that having a hardfile mounted does indeed allow me to run Doom Legacy on the PSP, among other numerous games which have a lot of filesystem I/O, whereas having only a folder mounted results in one of these said crashes.

The speed is something i'll just have to deal with - nothing is perfect and I ain't complaining. In the possible future I may take a crack at the IMGMOUNT code though, if I could be bothered. 😜

Thanks for your responses wd. I'll leave this thread open in case I come across anything worthy of note in regards to harddisk image speed (mainly for others' references).

Regards,
CosmicDan

Reply 5 of 10, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

iirc crazyc is still using (rather) old sources for his port (0.71?) so be sure
you update to the current cvs sources if that's possible/feasible as some
bugs have been fixed regarding fat drive handling.

Reply 6 of 10, by danielc

User metadata
Rank Member
Rank
Member
wd wrote:

iirc crazyc is still using (rather) old sources for his port (0.71?) so be sure
you update to the current cvs sources if that's possible/feasible as some
bugs have been fixed regarding fat drive handling.

Hey thanks for that tip - it is indeed based on 0.71 so I will definately get on that! I'm using the 0.72 release on Win32 for my testing, but I'll probably spend a few hours checking out all the changes between then and the current CVS.

CrazyC is clever enough to provide it as a simple patch so I shouldn't have too much trouble - except that I always developed under Windows, never gotten that deep in Linux and Cygwin is having major errors compiling the PSP-patched DOSBox, so i'm just using his pre-built binary for now (until I can figure it out). I noticed that even the official DOSBox Wiki doesn't mention Cygwin for Windows, it references MinGW instead, but the PSP toolchain probably is best supported on Linux anyway.

Anyway that's off topic, but great to know all that - thanks again wd 😀

Regards,
CosmicDan

Reply 7 of 10, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

It won't be as easy as applying the patch, as a lot has changed in-between.
Please be sure to tell crazyc that you will/might be working on upgrading
the sources to the cvs. If you need help just ask.

Reply 8 of 10, by danielc

User metadata
Rank Member
Rank
Member

Will do. You can lock this thread now, i've updated the title and there's no real reason to keep this open (unless you can think of a reason). I mean... my question was if I did something wrong or if it's expected, and yes it's expected. Resolved 😜

I'll can always start a new, more specific thread if I have more questions. Thanks again =)

Regards,
CosmicDan

Reply 9 of 10, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

If you know and use Cygwin, then MinGW is very similar.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 10 of 10, by danielc

User metadata
Rank Member
Rank
Member

Oh OK. Yeah will Cygwin is just a Linux emulator (sort of) isn't it? And so is MinGW? Maybe i'll take a look. Thanks!

Regards,
CosmicDan