Reply 40 of 51, by mnn
Well it is totally independent which drive I use to mount the folder as long as I do it manually. Using Autoexec section or some BAT automation crashes the whole thing up. I think this could (finally) be DOSBox issue.
Well it is totally independent which drive I use to mount the folder as long as I do it manually. Using Autoexec section or some BAT automation crashes the whole thing up. I think this could (finally) be DOSBox issue.
hmm com files being executed from bat files mess up the memory layout ? Well it is at least a direction for somebody to try to reproduce it
Water flows down the stream
How to ask questions the smart way!
It is hard to reproduce, because even I have problems to reproduce it 😀 Sometimes manually mounting as non-C drive works sometimes don't (C works always). Now, I was able to freeze DOSBox running BAT file (unmodified, which worked before) 😀 DOSBox is real mystery to me now.
EDIT: DOSBox freezes always now running BAT file, I don't know why, I restarted PC, so far nothing works.
please give us the contents of the batch file (or is it any batch file?)!
Any batch file freezes DOSBox, that's the problem. It seems I will have to manually mount each directory of each game I will play.
this sounds very strange and not normal Dosbox behaviour. Does a simple batch file with just the content
intro
freeze as well?
If not please give us any example of a freezing batch file.
If it does freeze, then there is something seriously wrong on your end.
Who made those BAT-files, why, and how?
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
Yeah, sorry my bad. Those batch files just called (not on purpose) recursively that's why it was freezing. Anyway thanks for help.
You are really resistant to help, aren't you? All questions aimed to help you get ignored, at least the important stuff (like the contents of the batch files, or running mem before and after...). Something to remember next time...
1) I didn't ignored anything. Don't assume anything.
2) Contents of batch files are irrelevant, they recusively called themselves (by mistake).
3) I did run mem before and after, you've been sleeping through that part of this thread.
4) Just remember... I''ll remember not to listen to guy like you.
1) I didn't ignored anything. Don't assume anything.
-> I just went by what I read
2) Contents of batch files are irrelevant, they recusively called themselves (by mistake).
-> Since they called recursively themselves the contents WERE relevant
3) I did run mem before and after, you've been sleeping through that part of this thread.
-> you never reported back on this except for
Well it is totally independent which drive I use to mount the folder as long as I do it manually. Using Autoexec section or some BAT automation crashes the whole thing up. I think this could (finally) be DOSBox issue.
and
It is hard to reproduce, because even I have problems to reproduce it Happy Sometimes manually mounting as non-C drive works sometimes don't (C works always).
This isn't much of a report, is it?
4) Just remember... I''ll remember not to listen to guy like you.
-> your loss, since guys like me are the ones that actually try to help guys like you...
2) Contents of batch files are irrelevant
If somebody like Dominus asks for it, there's a reason even if YOU don't understand it.
I''ll remember not to listen to guy like you.
Nothing to add then.