No error message from mount when used with unknown -type option?
Posted on 2007-03-07, 08:28
Re: CD-ROM issues in OSX
Re: CD-ROM issues in OSX
Posted on 2007-03-07, 08:27
You were sooooo close, but there is no cigar for you 😀 It is -t, not -type. Seems like DOSBox silently ignores the unknown -type option. It really should give an error IMNSHO.
Re: System shock 1
Posted on 2007-03-06, 23:15
You are mounting the virtual C-drive wrong. Try removing the last directory from the mount-path.
Re: crash
Posted on 2007-03-06, 23:09
No, this is either 1) A problem caused by the status-window going full screen, or 2) A problem with your video-drivers. Go to Start => Programs... => Accessories. Right-click on Command Interpreter, select Properties, go to the Options tab, and select Windowed-mode instead of Fullscreen. Press Apply …
Re: New DOSBox Frontend - DOSBox Game Launcher
Posted on 2007-03-06, 21:45
XulChris wrote: Okay, now I have run into another problem. The frontend expects to find a dosbox.conf file in the same directory as the dosbox executable. In what situation do you experience this problem?
Re: crash
Posted on 2007-03-06, 21:32
Your DOSBox directory should only contain these files: 2007-03-02 12:26 capture 2007-03-02 12:26 zmbv 2007-03-02 11:43 6 863 dosbox.conf 2007-03-02 11:18 326 656 SDL.dll 2007-03-02 11:18 13 312 SDL_net.dll 2007-03-02 11:18 3 107 840 dosbox.exe 2007-03-02 12:26 34 358 uninstall.exe 2007-03-02 11:03 …
Re: crash
Posted on 2007-03-06, 21:17
dbarton wrote: Does dfend change dosbox in some way? We don't know. Ask the author of D-Fend. dbarton wrote: I assume it just loaded with it as front end. Remember: assume rhymes on makes an ass of u and me. Never ass-u-me. Test, examine, and know.
Re: crash
Posted on 2007-03-06, 21:07
The full-screen window is the DOSBox status-window and the messages you saw are perfectly normal. But it is not normal for the status-window to fill the whole screen. It should only be slightly larger than the main DOSBox window (unless you yourself have modified the settings for your CMD-windows?). …
Re: crash
Posted on 2007-03-06, 20:48
I agree with wd - there is a lot of files in that directory. Looks like something that belongs to D-Fend?? Did you install D-Fend into the same directory as DOSBox-0.70? You shouldn't do that. If you did, you should export all your settings, uninstall D-Fend and completely remove the DOSBox-0.70 …
Re: crash
Posted on 2007-03-06, 19:47
Go to Start => Run ... => Cmd In the Cmd window, do a C:\> chdir /d "%ProgramFiles%\DOSBox-0.70" C:\> dir dosbox.exe C:\> dosbox.exe If DOSBox now fails to startup, please copy/paste the result from the dir command to this thread.
Re: dosbox 0.70 and core=auto
Posted on 2007-03-06, 19:25
How hot do your CPU become?
Re: crash
Posted on 2007-03-06, 19:21
dbarton wrote: If I delete DOSbox, reinstall, and run, I get a crash right away How do you "run" ? dbarton wrote: Now and again, I can start up DOSbox all alone, How do you "start up" ?
Re: compiling problem of franpa
Posted on 2007-03-06, 15:22
wd: Did you try single quotes? Just did - no change. gulikoza: why use spaces in the first place? Primarily because my HOME directory contains spaces. Second, because I like to bash programmers that naïve thinks the world is a simple place. Ever since I spent hours porting VAX-code with assumed …
Re: compiling problem of franpa
Posted on 2007-03-06, 15:07
Baaaahhhh!!! $ make install DESTDIR="/path/with spaces in" make[3]: Entering directory `/mingw/dosbox-0.70/src' /bin/sh ../mkinstalldirs /path/with spaces in/usr/local/bin mkdir -p -- /path/with spaces in/usr/local/bin /bin/install -c dosbox.exe /path/with spaces in/usr/local/bin/dosbox.exe /bin/ …
Re: compiling problem of franpa
Posted on 2007-03-06, 15:03
gulikoza: Yep! DESTDIR seems safe to use. From the automake manual: Staged installs Automake generates support for the DESTDIR variable in all install rules. DESTDIR is used during the make install step to relocate install objects into a staging area. Each object and path is prefixed with the value …
Re: compiling problem of franpa
Posted on 2007-03-06, 14:22
> MiniMax: most makefiles support DESTDIR parameter. Hmm - who/what implements that? I have never examined how the whole automake/configure complex works. Is DESTDIR something that automake provides? Or is it something the maintainer of makefile.am(?) is providing? I don't want to rely on something …
Re: compiling problem of franpa
Posted on 2007-03-06, 12:59
I guess I can use just about any SDL-version. My interest is in defining a build-environment (MSVC version, gcc version, SDL version, g++ version, automake version, etc) that matches what was used to build the different, official 0.70 releases. Setting --prefix=/some/empty/dir would allow me verify …
Re: Hard Nova - New problem - can't save - only in v0.70 but not v0.65
Posted on 2007-03-06, 12:51
No suggestions right now. But a game that behaves worse in 0.70 than in 0.65 is always interesting for the developers, so I will add Hard Nova to the list of "Broken in 0.70". There is no gaurantee that HN will be fixed for 0.71 though - it really depends if some of the developers take an interest, …
Re: compiling problem of franpa
Posted on 2007-03-06, 11:51
Anything is possible. I just prefer to do things 'right' instead of merely 'work'. And the 'right' way is for each product (like SDL) to install its product-specfic include files in /usr/include/ (or /usr/local/include/ ). It makes for less of a surprise and gotcha when things are configure in a …
Re: compiling problem of franpa
Posted on 2007-03-06, 11:44
gulikoza's sdl-config does this: --cflags) echo -I${prefix}/include/SDL -D_GNU_SOURCE=1 -Dmain=SDL_main The problem is, that SDL's make native copies all the include files directly to /usr/iinclude, and not to /usr/include/SDL. Hence my note to edit SDL's Makefile to do 2 copy-operations: 1. Copying …
Page 165 of 241