Did you mount another location as another drive to use for the install?
And are you trying to install to that drive instead of the drive mounted from the ISO?

See my FAQ.doc on harddrive sizes. More then the limit of 105MB is probably needed for the installer to work, maybe because it expects sound files to be copied wich could have been cut from your version.

Your real harddrive freesize isn't used in DOSBox.

Also as it is an ISO, you need to mount both your fictive harddrive and your CDROM drive. See the FAQ.doc and the readme for more info.

Erik.

I have a similar problem, but that occurs later.

I have used Dosbox for a while now and managed to make most games work, if the list shows them compatible.

However, I can't get Crusader no Remorse to work.

Unlike Baphomet, I installed the game with no problem, but when I start it, I get the error message: Halted File crusys.c, line 280 you need at least 15 megs of free hard drive space.

The game is already installed, (full install) and there is a lot more space than that on my D drive. What is happening and what can I do?
I already fiddled a lot with memory settings and cycles, I tried loadfix, partial install, I read the faq that says crusader needs XMS (Its also said in the documentation to the game), tried mounting everything as hard drive D (and C) and now I'm out of ideas.

I use dosbox 0,65, with D-Fend as front-end. I mounted the folder D:dosgames as drive D, my cd-rom E as itself. The game is the real CD (version 1,21).
My PC is: windows XP, 1200mhz, 480ram My hard drive is split in 2, C and D, both with plenty of space.

If the game had low compatibility, I would simply say it doesn't work on dosbox and play something else, but the comments say it works great, so there must be something to do! (I even tried it on dosbox 0,63, since that's the version the comments say it worked on, but no difference.)

Thanks a lot, a solution here would probably help for other games later too, so I would be doubly pleased and I remember crusader as awesome when I played it so many years ago.

Some games gets confused by tooo much free space, and errornously reports it as a too little free space problem.

Read the README - there are options for you to limit the amount of free space that DOSBox reports for a drive.

D:dosgames as drive D

Mount it as C drive and/or reinstall the game inside dosbox.[/quote]

First, thanks for the speedy reply, I appreciate it! Especially since I'm making progress!

According to both advice, I tried installing and running the game without using the frontend. After a bit of thinkering, (my dos days are long behind me, I'm afraid!) I managed to install drive D (hard drive) as drive C and E (cdrom). I used the freespace command (once I figured it out!) to limit drive space arbitrarily to 120mb. (Now I know why I'd want to do that!) I can't get the line to work with C being D:dosgames, so I used my entire drive D as C. Should not be a problem. I hope.

I then installed the game directly from dosbox. Again there seems to be no trouble. And the game actually started this time! It works horribly badly, and I will have to tweak settings. I suppose 3000 cycles is too low for such a late dos game.

I just need to figure out how to change that without the frontend, and how to make dosbox remember my mountings. I have to remount E and C each time I open it, and I'm not sure if that's normal. If I'm having too much difficulty, I'll get back to you on this, but I should manage.

Fortunately, crusader is worth all that thinkering, and what I learned today will speed up installing lesser games later.

Thanks a lot for the help, and for a great program!

Without the frontend you enter your settings in the [autoexec] section of dosbox.conf.

3000 cycles is way too low for Crusader. Try setting core=dynamic and cyles=auto in dosbox.conf.

Surnis wrote:

I can't get the line to work with C being D:dosgames, so I used my entire drive D as C.

Try with mount C D:\dosgames -freesize ....

Surnis wrote:

Should not be a problem. I hope.

It is not recommended to mount the whole physical drive. A small error in how you use DOSBox, and you risk deleting the entire physical drive. Much better to only mount a sub-dir.

I can't get the line to work with C being D:dosgames, so I used my entire drive D as C.

doesn't this work?

mount c d:\dosgames

mind that you use the real : and not something looking like the one Steven hada problem with at Directory Doesn't exists!! Going Nuts! 😀
With Dosbox 0.65 run it at cycles=auto and core=dynamic to achive maximum performance.

Edit: wrote this while the answer before me was not ye posted 😀

I'm afraid I do not know how to get in dosbox.conf. Typing it doesn't seem to work. It sounds like toolbar options, but I have no toolbar in dosbox. I suppose it refers to the second window that opens in the back, but I can't write in this one.

In the meantime, I found the line in the readme that says how to place the cpu cycles as, in the exemple 10000. I replaced the 10 000 by auto, and it was acepted. The game still stutters a lot, however, (and the cinemas are even worse) so I'll be trying manual numbers till I get it right. (10 000 is not it either)

I'll try if I can replace "cycles" by "core" and "10000" by "dynamic", to follow your suggestion. Hope it works.

I also found out that not only do I have to remount my drives, I also have to reinstall the game each time I reopen dosbox. Is there a way to save the profile as with the frontend and avoid this? It gets annoying reinstalling everything between each cycle number tried!

I realise that this topic is getting out of subject, since the "insufficient hard drive" trouble is settled, but I can't really reply somewhere else and lose you! Sorry.

Thanks for helping. I was going nowhere alone. Now, even being able to hear the stuttering intro music brings back a wave of nostalgia...

About the dosgame subject: (sorry guys, Your reply had not yet entered when I wrote my earlier message)

I think I had tried that line "mount C D:\dosgames -freesize 120"
and that it didn't work, but I was trying so much stuff that I may have made a mistake. (perhaps I had already mounted C as D:\dosgames without the freesize earlier, and that's why it refused? I can't remember for sure.

Still, I take into consideration your advive not to mount the whole D drive. Since I have to remount every few minutes anyway, I'll try again next time.

Thanks. I am really amazed by the great support I'm getting in this forum!

did you read the Readme that comes with Dosbox?
start Dosbox, dont' mount anything and enter
config -writeconf dosbox.conf
Then close Dosbox again. In the folder where Dosbox is installed to you should have now a file called dosbox.conf. Open this with Notepad.
Then use all the advice given on what to do with dosbox.conf 😀

I also found out that not only do I have to remount my drives, I also have to reinstall the game each time I reopen dosbox. Is there a way to save the profile as with the frontend and avoid this? It gets annoying reinstalling everything between each cycle number tried!

You are doing something wrong then. Why do you think you have to install it again. What does the game say that makes you do that?

Surnis - check my signature. And read the 60 seconds guide. It is great! (I wrote it 😀 )

I did read the readme file, and I dont see anything about this config stuff? Perhaps my readme is not complete?
Still, I followed your instructions and wrote two lines at the bottom. core=dynamic and cycles=auto. I don't know if core=dynamic changes anything, but the cycles were writen as auto in the blue title bar, so I guess I have it right. (But it still stutters.)

About reinstalling the game: Earlier, I kept getting the error message:
"unable to open file (null), in file file\fastflex.C, line 38." when I typed crusader on C: after mounting the drives. However, I tried it just before writing this, and it started. Coul it be because I modified the config? Doesn't seem related, but who am I to say? I hope it will stay this way.

About the 60 seconds guide: I seem to remmeber scanning this yesterday about the hard drive space problem, but not yet about this subject. You guys are replying too fast! I don't even have time to try to find solutions by myself anymore! 🤣 I'll get to it as soon as I find it again!

Thanks again!

Surnis wrote:

I'll get to it as soon as I find it again!

Find?? HELLO?? Read my signature (below)

The stuttering occurs due to your 1200 MHz cpu. I guess it's a bit too slow to run DOSBox at the speed required for Crusader.

Try ykhwong's latest CVS build, it's much faster than the original 0.65 release and works fine for me:
http://ykhwong.x-y.net/cvs/frame.html

("normal" daily builds w/o glide emulation etc.: http://builds.tharos-online.de)

Download the dosbox.conf attached to my post and put it into your DOSBox folder. I've configured it to use your real d:\dosgames as drive C and your real CD-ROM E as CD-ROM drive D. I can start Crusader without the freesize command, but you might want to add it if you encounter any problems.

Oh yeah cool idea recommending highly modified cvs builds to
somebody who has problems geting mounting correctly.

There are NO speed problems with crusader under 0.65
if configured correctly.

yep, if the PC is 1200 MHz and Crusader is too slow at with cycles=auto and core=dynamic then no CVS build is likely to change that.

Also, good idea to provide a preconfigured dosbox.conf, but when you do this, it is better to only give a dosbox.conf in which only the things you want to chnage are written. The conf you attached is a problem child, beginning with
windowresolution=960x720 and then all the special ykhwong experimantal stuff is in it...

Well, it was just a quick idea, because this conf file works fine for me. And I fail to see why I shouldn't recommend a CVS build that's not causing any problems in this specific case. He can always go back to the official 0.65 release if there's something wrong.
I still believe that a 1200 MHz machine is probably a bit too slow to play Crusader. I may be mistaken, but the latest CVS builds seem to run faster, especially in SVGA mode. Anyway, it wouldn't hurt to try, would it?