Re: some notes regarding sound and dosemu
hi dave, On Tue 08 Jun 04, 11:08 AM, Dave Phillips <[EMAIL PROTECTED]> said: > Greetings: > > The other day I read some posts on this list regarding failures to get > sound and music working for certain MS-DOS games. I'd like to know what > some of the major offenders are, I'd be willing to test them here in my > studio. I have complete MIDI I/O now with dosemu, and I've begun to test > its audio support as well. Yesterday I tried running the following > programs, with the results indicated: > >Quake sound was good, but no music (I'm missing the MSCDEX file) i just installed the developer's dosemu (1.3) along with the most recent freedos on my gaming machine. the freedos version came with shsucdx, which is a drop in replacement for mscdex. if you have a recent version of freedos, it should have shsucdx. if not, you can download it from: http://www.geocities.com/jadoxa/shsucdx/ or (presumably) the freedos site. let me know if you want instructions on how to set it up. >Paul's Sound Designer 2.2 very good audio output >Well-tempered Fractal program runs but no sound yet > > I've been running these programs as well: > >Sequencer Plus Gold MIDI sequencer, works perfectly >Drummer MIDI rhythm programmer, works well, but has mouse problems > (the mouse works but doesn't scale to window size) >Sound Globs boots but doesn't work (no sound) >M/pc boots, but I haven't figured out how to get a mouse working > in it (and it really needs the mouse) are any of these programs freeware / abandonware? if so, i'd like to try them out myself. > As you can see, my interest has been primarily in the MIDI side of > things. I'm interested in testing some more games, but I need some > recommendations. Anyone ? sure. i'll write about my personal experiences with gaming under dosemu. redneck rampage is a classic. built on the BUILD engine, written by a teenager as (what i think was an) after school programming hobby. the BUILD engine was problematic for linux game porters. it was written in an age before code re-usability was a common practise. the BUILD engine itself was open sourced and ported by programmers at icculus.org. unfortunately, games using this engine (redneck rampage, redneck rampage rides again, duke nukem 3D and a bunch of other lesser known FPS) had just enough code written into the BUILD engine that it wasn't just a simple matter of "taking the data file and running it with the engine) like you can with modern FPS like doom and quake. the games themselves needed to be open sourced because their data files contained engine code, not just game data information. i played redneck rampage under dosemu 1.1 (where i had to patch dosemu using stas's sound patches), and am playing it again under dosemu 1.3 (where i assume his patches are in because i didn't have to patch dosemu to get sound working). in both versions, the sound is anywhere between decent and good. there's a little crackling here and there. not enough to be annoying. in dosemu 1.3, something unexpected happened. apparently, there's sound tracks on the CD. i never knew that before and it as a pleasant surprise (until i realized i don't know how to shut it off other than to take the CD out of my computer). - if redneck rampage is funny and satirical, then redneck rampage rides again is even funnier, and is better designed. i played it once under dosemu, and sound worked the same as with redneck rampage. - there's the original doom and all the games written using the doom engine like like heretic, hexen and others. i've played the original doom under dosemu 1.1. sound/music worked fantastically. however, doom ports such as doom legacy and prboom (used to be lxdoom) are SO good, that it's just not fun to play the original anymore. to be able to use mouselook and having networking so easy and flawless (as opposed to that IPX nonsense) just ... make playing the DOS version really pointless. you can get shareware versions here: http://www.dosgames.com/g_3d.php -- then there's the classic, duke nukem 3D. it uses the BUILD engine, and is a classic game for dosemu gamers. like reneck, it's supposed to be satirical and funny, although less actual humor. i played it under dosemu 1.1 and sound / music worked great, although the subtle periodic crackling that i mentioned in redneck was present here. you can download shareware here: http://www.dosgames.com/g_3d.php like doom and friends, it's been open sourced and some REALLY good ports have been made. unlike doom, the BUILD engine had mouse look, but it sucked. well, back in the day it was awesome, but the perspective when looking at any angle but 0 degrees was really distorted, as if you were looking through a lens. the new ports are very clean and have excellent mouse look perspective. it makes playing the original ... well, a little sad. - my most recent attempt at dosemu is "lure of the
alone in the dark kills dosemu
I have a demo of Alone In The Dark (classic game that started the Point and Click Horror Adventure genre) that seems to kill dosemu. Running dosemu with "xdosemu -D9S -o logfile", the relevent lines seem to be: SIGILL while in vm86() OUCH! attempt to execute interrupt table - quickly dying leavedos(57|0x39) called - shutting down leavedos() called from within a signal context! This is the first time I've ever seen a SIGILL. Didn't even know what it was when I first saw it. This is a demo that's played by many other people (who prolly aren't using dosemu). It shouldn't be doing this. Is there anything further I can do to figure out what's going on? The demo is only 700kb; I can upload it somewhere... Thanks, Pete -- In theory, theory and practise are the same. In practise, they aren't. GPG Instructions: http://www.dirac.org/linux/gpg GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Is dosemu build system not working correctly?
I think there's a problem with the dosemu build system. I'm using Debian testing. When I build with "linkstatic off", everything is fine: configure: Linking for shared libraries... checking for vga_simple_init in -lvga... yes configure: Compiling with svgalib support... checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for XOpenDisplay in -lX11... yes configure: Compiling with X support... checking for X11/extensions/XShm.h... yes checking for X11/extensions/xf86vmode.h... yes However, when building with "linkstatic on", the static libraries aren't found: configure: Linking statically... checking for vga_simple_init in -lvga... no configure: Compiling without svgalib support... checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include checking for dnet_ntoa in -ldnet... no checking for dnet_ntoa in -ldnet_stub... no checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for XOpenDisplay in -lX11... no checking for XCloseDisplay in -lX11... no checking for main in -lXwindow... no configure: Compiling without X support... I have the following packages installed: libx11-6, libx11-dev, x-dev, xlibs-dev, libsvga1-dev The libraries really are on my system: # locate libvga.a libX11.a /usr/lib/libvga.a /usr/X11R6/lib/libX11.a But it looks like they (the static versions) aren't being found. Is this a known issue? Do I have the correct libraries installed? Thanks, Pete -- GPG Instructions: http://www.dirac.org/linux/gpg GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D Good, Fast, Cheap. Pick any two (you can't have all three) --- RFC 1925: The Twelve Networking Truths (The 7th truth) - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
adding a drive
Hi there, The concept of a built-in config file is confusing to me. Without any changes: C: points to /usr/local/share/dosemu/freedos D: points to $HOME I'm unsure about how to add a new "drive" that points to /usr/local/dos, where I intend to install programs. I tried: ln -s /usr/local/dos ~/.dosemu/drives/e That didn't do anything. Then in /etc/dosemu/dosemu.conf, I wrote: $_hdimage = "/etc/dosemu/drives/*" In /etc/dosemu/drives are the following links: c -> /usr/local/share/dosemu/freedos/ e -> /usr/local/dos/ But now, C: points to /usr/local/share/dosemu/freedos D: points to $HOME E: points to /usr/local/share/dosemu/freedos/ F: points to /usr/local/dos which is good, but I'd rather not have dosemu/freedos repeated. If I remove /etc/dosemu/drives/c, then dosemu won't boot at all (it can't find an operating system). So I found a way that works, but it duplicates a hard drive. So what's the proper way of adding a drive to the system? Thanks, Pete - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
xdos missing?
I just built dosemu 1.3.0, and xdosemu seems to be missing. It didn't get installed into /usr/local/bin the way dosdebug, dosemu and dosemu.bin did. It doesn't appear to be in dosemu-1.3.0/bin the way the other make targets did. Any ideas what happened to it? Is there a compile time option to surpress building xdosemu? Thanks, Pete - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Latest Stable Version of Dosemu
the most obvious thing to try would be www.dosemu.org, kinda like www.ibm.com, www.microsoft.com, www.samba.org. have you tried www.dosemu.org? it might work. but if www.dosemu.org doesn't work, www.google.com certainly will pete begin John J. Boyer <[EMAIL PROTECTED]> > Hello, > > please refresh my memory on the latest stable version of dosemu and on the > uRL from which it can be downloaded. > > Thanks, > John -- First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi, being prophetic about Linux. Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: mouse grabbing gotcha (was: dosemu 1.1.3.9 user report)
omg. getting dosemu has been bad for me. i just spent the last 3 hours playing non-stop redneck rampage. :) so far, it has been nearly flawless. it runs better under dosemu on a celeron 550 than it does under microsoft on a celeron 450 (my girlfriend has a dual boot that i used to compare). dosemu hung once in 3 hours of playing, but it didn't take out my system. i flipped to virtual console and killall'ed it. holy moley. thank you guys. i really appreciate all the work you've done! begin Bart Oldeman <[EMAIL PROTECTED]> > On Tue, 17 Dec 2002, Stas Sergeev wrote: > > > Peter Jay Salzman wrote: > > > i guess enlightenment traps cntl-alt-home, because the key combo won't > > > let dosemu grab the mouse. > > > however, it DOES work with twm. > > Can you figure out a more reliable > > combination then? > > Set $_X_mgrab_key to, say, "Scroll_Lock" > > or "Pause" and if there is something > > that works everywhere, then I think the > > default "Home" should be changed. > > Pause is already taken as being a force pause (freeze). > One problem is that you can define just about any keycombo in some of > these window managers, so there is nothing that works everywhere; however > some combinations are used more often than others. i'd have to agree. i'm not hip onto all the window managers; enlightenment and twm are the only ones i use. btw, for gaming purposes (and i guess this is general, but is more appropriate for gamers), placing the line: exec xdosemu in .xinitrc, restarting X, and using ctl-alt-+ to cycle through video modes till xdosemu fills the entire screen gives the illusion of fullscreen. it's not *true* fullscreen in the sense of SDL's "fullscreen" bit when you initialize SDL video, but honestly, you can't really tell the difference. > ctrl+alt+scroll_lock might be something that makes sense though, since > you're locking the mouse. something to think about post-1.1.4 :) i'm not sure if there's any safe keycombos to use, but frankly, ctl-alt-home is pretty exotic. i'd recommend keeping it or perhaps using ctl-alt-scroll_lock, which is definitely more intuitive. i know a lot of people who'd love to play these old games again, but weren't able to get dosemu to run the games. the doom in linux howto is very good, but there's no reason why the advice applies just to doom. most of it applies to all games. i used that howto as a guide, but did other things like use a more recent freedos and used 1.1.3.9 (which came out after the howto was last updated). i'm detailing everything i did in a general DOS gaming under linux HOWTO. i'll having something useful by this evening after i come back from our local LUG meeting[1]. pete [1]- funny story. tonight the guest speaker is talking about C99. while my friend was putting up flyers advertising the event, an asian guy asked him what was going on. they started talking, and it turns out the guy is on the C99 standards committee. :) it's be cool if he came to the meeting. :) -- First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi, being prophetic about Linux. Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
mouse grabbing gotcha (was: dosemu 1.1.3.9 user report)
begin Bart Oldeman <[EMAIL PROTECTED]> > On Mon, 16 Dec 2002, Peter Jay Salzman wrote: > > > have you been able to have xdosemu grab the mouse? i've been having > > trouble playing redneck rampage because if the mouse "moves over" too > > far left or right, the mouse leaves the xdos window. > > try ctrl-alt-home. I noticed in your dosemu.conf that you uncommented the > mgrab_key setting, but it should work by default. > > Bart i guess enlightenment traps cntl-alt-home, because the key combo won't let dosemu grab the mouse. however, it DOES work with twm. these are the only 2 wm's i use. :) also, running DOSEMU as your "window manager" by running "exec xdosemu" from .xinitrc also works. :) pete -- First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi, being prophetic about Linux. Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
HOWTO correction - broken link
hi all, in http://dosemu.sourceforge.net/docs/HOWTO/dosemu-HOWTO-1.html#ss1.4 the link to bochs: www.bochs.com should be changed to: http://bochs.sourceforge.net looks like www.bochs.com is no more. at least, not anything useful. :) pete -- First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi, being prophetic about Linux. Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
subscription for dosemu?
has any of the developers thought of selling dosemu support ? would the transgaming business model work with dosemu? i'm pretty sure there wouldn't be enough people to support a full time staff like winex, but i think something like that would make the users very happy and encourage faster development of dosemu. just a thought. although i'm a grad student and don't have much money, i'd certainly be willing to pay 1) for support and 2) to help the dosemu project along to encourage more development. i'm sure others would do the same. pete -- First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi, being prophetic about Linux. Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dosemu 1.1.3.9 user report
hi jan,
IIRC, there was talk about important dosemu related patches that are
present in the most recent kernels. i think it was said that the
patches have been in the ac kernels for awhile, but have just recently
made it into the vanilla 2.4 kernels.
i have no idea what the patches do, but you can try using 2.4.20 and see
what happens.
btw, it sounds like you're playing in an xdos box. have you been able
to play at all in console?
have you been able to have xdosemu grab the mouse? i've been having
trouble playing redneck rampage because if the mouse "moves over" too
far left or right, the mouse leaves the xdos window.
pete
begin Jan Willem Stumpel <[EMAIL PROTECTED]>
> According to "top", 1.1.3.9 takes up 99 % CPU even when just
> displaying the C:> prompt.
>
> 1.1.3.7 does this also; but 1.1.3.0 and 1.0.2.1 do not. They
> hardly use any CPU when just displaying the prompt (or waiting for
> a keystroke in a text-mode program).
>
> Wolfenstein 3D:
> 1.0.2.1, 1.1.3.7, 1.1.3.9 play with $_sound = (off) .
> 1.1.3.0 hangs (with or without sound) after displaying the
> start-up (setup) screen. Control-Alt-PgDn is the only way out.
> 1.1.3.7, 1.1.3.9 hang with $_sound = (on) .
>
> Duke Nukem3D:
> 1.0.2.1 plays fine without sound.
> 1.1.3.0 plays without sound, but after a short while suddenly
> disappears (no more dosemu window).
> 1.1.3.7, 1.1.3.9 play, with $_sound = (on) and soundblaster
> selected in Duke Nukem Setup. I can see *and hear* the demo
> (sounds, no music). When I want to start a game, I can select the
> game type ("L.A. Meltdown" or whatever); however, when I try to
> select the difficulty level the program hangs.
>
> All this with kernel 2.2.18pre21, $_dpmi = (8192) , $_hogthreshold
> = (800).
>
> Regards, Jan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
First they ignore you, then they laugh at you, then they fight you,
then you win. -- Gandhi, being prophetic about Linux.
Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
success with redneck rampage and a few questions
hi all, redneck rampage runs great under an xdos box. actually, i can't believe how fast it is. the sound is great. very cool. i see a lot of improvements in dosemu since last year. two questions: 1. i already read in the mailing list archives that there is no full screen xdosemu. it sounds like there never will be a fullscreen xdosemu either. however, the game runs but no graphics show up on a console. i enabled svga in the configure process and made sure that svgalib shows up in ldd dosemu.bin. the game gives an error message "vesa driver for 640x480 not supported. i can hear the game fine; it's obviously running. just no graphics. i've attached my config file below. any advice? 2. playing in an xdos box wouldn't be so bad if it would grab the mouse. is there a way to get dosemu to grab the mouse exclusively? everytime i look too far left or right, the mouse pointer goes beyond the bounds of the xdos box and the mouse leaves the game. any way to bind the mouse exclusively to the game? pete # $_hdimage = "/root/dosemu/freedos" # $_hdimage = "/cdrom/FREEDOS/INSTALL/BOOTDISK/FLOPPY" # $_hdimage = "/cdrom/FREEDOS/FDOS/BIN" $_hdimage = "/root/bootdir" # # List of hdimages or boot directories under # # syshdimagedir (/var/lib/dosemu by default) # # assigned in this order such as # # "hdimage_c directory_d hdimage_e" # # Absolute pathnames are also allowed. # # If the name begins with '/dev/', then partion # # access is done instead of virtual hdimage such as # # "/dev/hda1" or "/dev/hda1:ro" for readonly # # Currently mounted devices and swap are refused. # # Hdimages and devices may be mixed such as # # "hdimage_c /dev/hda1 /dev/hda3:ro" # # Note: 'wholedisk' is _not_ supported. #$_hdimage_r = $_hdimage# hdimages for 'restricted access (if different) # #$_debug = "-a+cw" # same format as -D commandline option, ""="-a+cw". # # (but without the -D in front) #$_features= "" # list of temporary hacks, see release notes in $_features= "0:10" # list of temporary hacks, see release notes in # # the file ChangeLog. e.g "0:1 2:0", which means # # to set feature_0 to 1 and feature_2 to 0. #$_mapping= "" # preferred mapping driver, one of: # # auto, mapself, mapfile, mapshm #$_timint = (on)# emulate INT08 type timer interrupts #$_mathco = (on)# or off $_cpu = "80586" # CPU shown to DOS, valid values: "80[345]86" # # or "emulated" for non-native CPU (386 in this case) # #$_rdtsc = (off)# if possible use Pentium cycle counter #$_cpuspeed = (0) # 0 = calibrated by dosemu, else given (e.g.166.666) $_xms = (8192) # in Kbyte $_ems = (2048) # in Kbyte #$_ems_frame = (0xe000) $_dpmi = (0x16384) # in Kbyte (default is 0 if running suid-root) #$_dosmem = (640) # in Kbyte, < 640 #$_hardware_ram = ""# list of segment values/ranges such as # # "0xc8000 range 0xcc000,0xc" # #$_emusys = "" # empty or 3 char., config.sys -> config.XXX #$_emuini = "" # empty or 3 char., system.ini -> system.XXX # $_hogthreshold = (0)# 0 == all CPU power to DOSEMU #$_term_char_set = "" # Global code page and character set selection. # # "" == automatic, else: ibm, latin, latin1, latin2, # # koi8r # # # Character set used externally to dosemu #$_external_char_set = "" # # "" == use $_term_char_set one of else: # # "cp437", "cp737", "cp775", "cp850", "cp852", "cp857", # # "cp860", "cp861", "cp862", "cp863", "cp864", "cp865", # # "cp866", "cp869", "cp874", # # "iso8859-1", "iso8859-2", "iso8859-3", "iso8859-4", # # "iso8859-5", "iso8859-6", "iso8859-7", "iso8859-8", # # "iso8859_9", "iso8859-14", "iso8859-15", "koi8-r" # # # Character set used by dos programs #$_internal_char_set = "" # # "" == use $_term_char_set one of else: # # "cp437", "cp737", "cp775", "cp850", "cp852", "cp857", # # "cp860", "cp861", "cp862", "cp863", "cp864", "cp865", # # "cp866", "cp869", "cp874" # #$_term_color = (on)# terminal with color support #$_term_updfreq = (4) # time between refreshes (units: 20 == 1 second) #$_escchar = (30) # 30 == Ctrl-^, special-sequence prefix # $_rawkeyboard = (1) # bypass normal keyboard input, maybe dangerous #$_layout = "au
Re: segfault with backtrace and information
begin Peter Jay Salzman <[EMAIL PROTECTED]> > dosemu consistantly segfaults on one of my machines. > i'm using version 1.1.3.7 with the experimental sound patches under > vanilla 2.4.20. machine arch is AMD athlon 1st generation 1.4 GHz with > a 1st generation ATI radeon. sorry, this machine is running vanilla 2.4.19, not 2.4.20. pete - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
segfault with backtrace and information
dosemu consistantly segfaults on one of my machines.
i'm using version 1.1.3.7 with the experimental sound patches under
vanilla 2.4.20. machine arch is AMD athlon 1st generation 1.4 GHz with
a 1st generation ATI radeon.
the machine didn't oops.
backtrace is follows:
lucifer# gdb /usr/local/bin/dos-debug
(gdb) run
Starting program: /usr/local/bin/dos-debug
Linux kernel 2.4.19; CPU speed is 1300264000 Hz
Dosemu-1.1.3.7 Running on CPU=586, FPU=1
Program received signal SIGSEGV, Segmentation fault.
0x080aeda4 in real_yylex (yylval=0x4d003b) at lexer.l:707
707 yylval->s_value = strdup(&yytext[1]);
(gdb) bt
#0 0x080aeda4 in real_yylex (yylval=0x4d003b) at lexer.l:707
#1 0x08107251 in _IO_stdin_used ()
the area of code:
(gdb) l 707
702 {STRQUOTELESS} MAY_BEFORME {
703 yylval->s_value = strdup(yytext);
704 EXPRTYPE(yylval->s_value) = TYPE_STRQUOTELESS;
705 return(STRING); }
706 ${IDENT}MAY_BE {
707 yylval->s_value = strdup(&yytext[1]);
708 EXPRTYPE(yylval->s_value) =
TYPE_STRQUOTELESS;
709 return(VARIABLE);
710 }
711 $${IDENT} MAY_BE { enter_macrofile(&yytext[2]);}
(gdb) printf "%s", &yytext[1]
_DOSEMU_ORIG_PATH(gdb)
(gdb) printf "%s", strdup(&yytext[1])
_DOSEMU_ORIG_PATH(gdb)
(gdb) printf "%s", yylval->s_value
Cannot access memory at address 0x4d003b
(gdb) printf "%s", yylval->s_value
Cannot access memory at address 0x4d003b
(gdb) ptype yylval->s_value
type = char *
(gdb) p yylval->s_value = strdup(&yytext[1])
Cannot access memory at address 0x4d003b
i'm a bit confused at this point. it looks like the address returned by
strdup is no good, but i have no idea how that can be.
strace provides no help:
write(2, "Linux kernel 2.4.19; CPU speed i"..., 48) = 48
write(2, "Dosemu-1.1.3.7 Running on CPU=58"..., 41) = 41
brk(0x832d000) = 0x832d000
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
ltrace output pretty much confirms what the backtrace said:
strcmp("parser_version_3", "h_lucifer") = 8
strcmp("parser_version_3", "c_all") = 13
strcmp("parser_version_3", "parser_version_3")= 0
strchr(""/etc/dosemu.conf"", '\n')= NULL
__strdup(0x08329490, 10, 0, 0x080aa782, 0x08107251) = 0x0832cb78
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
dosemu works fine on my other machines. this seems to be a problem with
this machine only, but nothing about this looks arch dependent to me.
any suggestions?
pete
--
Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Doom in Linux HOWTO
hi stian, one comment -- you're walking people through installing bleeding edge dosemu, but there's a problem with the latest patchset 1.1.3 where the compiling of a bison file fails. the fix (in patch form) is here: http://article.gmane.org/gmane.linux.msdos.general/847 this link also mentions that dosemu users may want to use 2.4.19 or 2.4.20-pre since these kernels contain dosemu related patches. this email was written before 2.4.20 came out, so i'm assuming that 2.4.20 also contains the dosemu related patches. the patch i mentioned is summarized here: in bisonpp.pl, change the line: $rule =~ s/[ \t]*;\s*$//s;# remove trailing ';' to this: $rule =~ s/[ \t]*;\s*\n//s;# remove trailing ';' i'm only mentioning this because patch sets come out so infrequently with dosemu that some of your readers may need to know this for a little while. pete - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Doom in Linux HOWTO
because he wanted to detail doom under dosemu. :) sometimes this kind of reason is simply enough when you're talking about linux. btw, lxdoom is totally outdated. that project has merged with 2 other doom port projects and has formed prboom. i think doom legacy is the best; you have mouse look up and down (like quake) and can jump. pete begin phrostie <[EMAIL PROTECTED]> > sorry i'm late getting into this but why can't you run either: > > lxdoom-svga 1.4.4-7 > Svgalib binary for lxdoom > or > lxdoom-x11 1.4.4-7 > X binary for LxDoom > > do they not have needed features? -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
segfault: 1.1.3.7
system:
amd athlon 1.4
debian sid
linux 2.4.19 (linus, not ac)
steps taken to install:
As root:
1. In /root: dosemu-1.1.3.tgz, dpmi_sti4a.diff, patchset-1.1.3.7.tgz,
dosemu-freedos-bin.tgz
2. # tar zxvf dosemu-1.1.3.tgz
3. # cd dosemu-1.1.3
4. # tar zxvf ../patchset-1.1.3.7.tgz
5. # sh tmp/do_patch
This patches DOSEMU 1.1.3 to 1.1.3.7
6. # mv ../dpmi_sti4a.diff .
7. # patch -p0 < ./dpmi_sti4a.diff
8. Applied another bison related patch. See:
http://article.gmane.org/gmane.linux.msdos.general/847
9. # make (press enter when it asks you to)
10. # cp ../dosemu-freedos-bin.tgz .
11. # ./install_systemwide -fd dosemu-freedos-bin.tgz
As user p:
12. $ dosemu (hit enter to confirm)
dosemu printed some stuff then segfaulted:
/usr/bin/dosemu: line 402: 24578 Segmentation fault (core dumped)
$BINARY $MAINARGS "${par[@]}" 2>$LOG
this time, i scoured the mailing list archives. can someone help me
with this?
thanks!
pete
--
Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
never mind: compiling problem with 1.1.3.7
hi all, i haven't received a copy of the email i sent about the bison error in 1.1.3.7, but it's bound to appear sooner or later. just did a web search and found the patch to correct the problem. dosemu compiled just fine. so please ignore my last message. :) thanks, pete -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
compiling problems: dosemu 1.1.3.7
this compiles fine: 1. tar zxvf dosemu-1.1.3.tgz 2. cd dosemu-1.1.3 3. make (press enter when it asks you to) however, this errors out during compiling: 1. tar zxvf dosemu-1.1.3.tgz 2. cd dosemu-1.1.3 3. tar zxvf ../patchset-1.1.3.7.tgz 4. sh tmp/do_patch 5. make (press enter when it asks you to) here's the compiler error: bison -y -v -do parser.c parser.y parser.y:377.3: parse error, unexpected "|" parser.y:377.26-68: $2 of `line' has no declared type parser.y:378.20-63: $2 of `line' has no declared type parser.y:378.20-74: $2 of `line' has no declared type (mega snip) parser.y:796.7-57: $1 of `line' has no declared type make[3]: *** [parser.c] Error 1 make[3]: Leaving directory `/root/dosemu-1.1.3/src/base/init' make[2]: *** [base/init] Error 2 make[2]: Leaving directory `/root/dosemu-1.1.3/src' make[1]: *** [default] Error 2 make[1]: Leaving directory `/root/dosemu-1.1.3' make: *** [default] Error 2 i tried taking a look, but i've used flex and bison for one of my programs, a long time ago, and frankly, they're both still a big black bag of voodoo to me. :( any advice on what to do? i'd like to use 1.1.3.7 (and stas' patches) if possible. thanks, pete (who is now on the mailing list) -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
redneck rampage and dosemu
Hello all, I have the hankering for playing an old DOS game called "Redneck Rampage". It uses the same engine as Duke Nukem 3D. Has anyone reported success running this game under DOSEMU? Would it be better to try with DOSEMU stable 1.0 or developer 1.1.3? pete ps- Please cc me at [EMAIL PROTECTED]; I'm not on the list yet. Thanks! :) -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: cdrom question
begin Stas Sergeev <[EMAIL PROTECTED]> > Hello. > > Peter Jay Salzman wrote: > > C:\>mscdex /D:MSCD0001 /L:E > > Not enough drive letters available > >can someone help me resolve this error message? > Have you tried something like LASTDRIVE=Z adding in your > config.sys? thanks everyone. that worked. i can now access the cdrom drive. unfortunately, the system freezes up for something like 30 seconds when the cdrom is first accessed (or when i do a DIR in a cd directory that hasn't been cached yet). but one problem at a time... i'm going to try installing the sound patches next (unless someone tells me that the next version of dosemu along with the patches will be released soon). > >i never really used > >DOS, so i don't grok things very well. > For most Linux users DOS is mostly a legacy and dosemu helps > them to continue using what they could have lost otherwise > (for me it is a special backup hardware that doesn't have > a linux drivers). > But I am a bit curious about a reason why the one can > *start* using DOS under dosemu? The only reason I can > imagine is a good old dos games:) really, some of the older DOS games are classics. true classics. graphics got better, sound got louder, engine got smarter, but the originality and brilliance of things like tomb raider or redneck rampage or duke nukem can never be duplicated. my girlfriend has a win32 system, and i can't even play tomb raider on it because it doesn't support her ESS sound chipset... i was hoping to play this game under dosemu. pete - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
cdrom question
hi all, here's what i see when i boot dos or xdos: Linux DOS emulator 1.1.2.0 $Date: $ Last configured at Fri Jan 4 16:22:05 PST 2002 on linux DPMI-Server Version 0.9 installed Starting MS-DOS... [dosemu cdrom driver instsalled (V0.2)] C:\>path C:\;C:\dos-6.22;C:\utils;C:\dosemu C:\>mscdex /D:MSCD0001 /L:E Not enough drive letters available can someone help me resolve this error message? i never really used DOS, so i don't grok things very well. i assume drive letters can go from A to Z. currently, i only use C: and D:. here's autoexec.bat: path C:\;C:\dos-6.0;C:\utils;C:\dosemu mscdex /D:MSCD0001 /L:E and config.sys: devicehigh cdrom.sys here are some lines that look relevent in dosemu.conf: $_hdimage = "dos dosgames cdrom" $_aspi = "sg0:CD-ROM" can someone help me resolve the lack of drive letters for my cdrom? thanks! pete - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dosemu on debian
are you on x86 architecture? pete begin Carl D. Blake <[EMAIL PROTECTED]> > I tried the suggestion of getting the source from the dosemu site. I > compiled it and installed it without any problems I could see, but I > still have the same problem. dosemu stops with a Floating point > exception. Any other suggestions? > > On Tue, 2002-02-05 at 12:32, Peter Jay Salzman wrote: > > you may want to try dosemu from the dosemu site instead of using the > > debian package -- it's packaged kind of funky. and in setting it up, > > you'll learn alot about how dosemu works. > > > > begin Carl D. Blake <[EMAIL PROTECTED]> > > > I'm having a problem running dosemu V1.0.2.1 on a new Woody debian > > > install. When I execute dosemu I get the message about type ENTER to > > > start DOSEMU or C to cancel. When I type the enter key I get a > > > floating point exception error. If I run dosemu.bin directly, it > > > immediately returns Floating point exception. I'm using this with > > > freedos. Does anybody have any suggestions? - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Wabi for Linux -- WAS: MSDOS 6.22 running with/in Dosemu.
begin Matthew Nuzum <[EMAIL PROTECTED]> > On Tue, 2002-01-15 at 12:27, Bryan J. Smith wrote: > > Wabi was created by SCO unix in Santa Cruz, CA. They used to be the primary > commercial Unix on x86 hardware vendor. That was back in the days when MS > acutally worked with competitors such as Novel and SCO to provide a > workable solution for everyone. > > Caldera bought them mid last year. They got the whole kit 'n' kaboodle, I > guess. IMHO, Tarantella is the only tangible item of substance gained from > the deal. i was under the impression that wabi was written by sun microsystems? or is it that sun licensed it from sco? pete -- The mathematics [of physics] has become ever more abstract, rather than more complicated. The mind of God appears to be abstract but not complicated. He also appears to like group theory. -- Tony Zee's `Fearful Symmetry' PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Wabi for Linux -- WAS: MSDOS 6.22 running with/in Dosemu.
begin gaw zay <[EMAIL PROTECTED]> > On Tue, 15 Jan 2002, Bryan J. Smith wrote: > > > Justin Zygmont wrote: > > > ftp://solarflow.dyndns.org/pub/wabi > > > > - WINE (BSD) > > I thought Wine used the MIT license? winehq says: "The licensing terms are similar to X11.", and X11 uses the MIT license. so, yeah. i think you're right. otoh, i think BSD is similar the MIT/wine licenses. GPL is the odd man out. i can understand (but don't agree with!) microsoft's statement that the GPL is a virial license. pete -- The mathematics [of physics] has become ever more abstract, rather than more complicated. The mind of God appears to be abstract but not complicated. He also appears to like group theory. -- Tony Zee's `Fearful Symmetry' PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
sound questions
are the variables: $_sb_base = (0x220) $_sb_irq = (5) $_sb_dma = (1) $_mpu_base = "0x330" supposed to be emulated variables or are they supposed to reflect the actual settings of the soundcard of the system? for instance, my sound card is a PCI-128 which was assigned to irq 11. should $_sp_irq supposed to be 5 (which i think was hardcoded in the old ISA soundblasters) or 11 (which my system recognizes as the soundcard irq)? also, someone on the list sent me email saying that he thinks the sound code in dosemu is completely broken, as in, dosemu can't utter a peep right now. but he wasn't sure. is this pretty much the situation for dosemu 1.1.2? lastly, when i run redneck rampage, it bails with the following message: Cachesize = 3802576 Cacnum = 2 0- ptr: 0x4085b040, leng: 322560, lock: 255 1- ptr: 0x4691fb, leng: 3480016, lock: 0 Cache length sum = 3802576 i'm at an utter loss -- i don't know how to diagnose something i can't understand. can someone guess as to what's happening? pete -- The mathematics [of physics] has become ever more abstract, rather than more complicated. The mind of God appears to be abstract but not complicated. He also appears to like group theory. -- Tony Zee's `Fearful Symmetry' PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: MSDOS 6.22 running with/in Dosemu.
begin John Goley <[EMAIL PROTECTED]> > Hi Edward Mendelson, > > I think I remember you saying on list that you go Dosemu 1.0.2.1 running > with MSDOS 6.22. windows' dos isn't the best one to use. you also want to stay away from dos 4.x. > How did you do it? I am very new to Linux and Dosemu and need all the help I > can get. > > Trying version 1.0.2 with freedos on my new P4 1.7 ghz machine wouldn't work > at all. xdosemu said it was starting but would never give me a DOS box. > Never had this problem when I was using a AMD Athalon 1.2 ghz machine. > > Anyway my main question is how to get MSDOS to work rather than use the > provided freedos. > > Thanks for any help you could give me. well, i'm not edward and i don't know if this is the right way, but here's what i did. freedos was installed in /var/lib/dosemu/freedos, so i did: mv /var/lib/dosemu/freedos /root/oldfreedos # keep a copy somewhere mkdir /var/lib/dosemu/freedos and put command.com, io.sys, msdos.sys, autoexec.bat, config.sys and all the other DOS programs in /var/lib/dosemu/freedos. you can take them all from windows if you want dos 6, or you can take them from a dos 5 floppy. your choice. after awhile, i thought it was kind of goofy to have dos 5.0 in a directory named "freedos". so in /etc/dosemu/dosemu.conf, i changed: $_hdimage = "freedos dosgames cdrom" to $_hdimage = "dos dosgames cdrom" and renamed /var/lib/dosemu/freedos to /var/lib/dosemu/dos. note that the first directory in $_hdimage becomes your C: drive, and that's where DOS should go. so the short answer is: put whatever DOS you want to use in that directory. MAKE SURE to not mix up files from different dos's. also, the directories in $_hdimage are relative to $DOSEMU_LIB_DIR, defined in /var/lib/dosemu/global.conf. this may all sound complicated, but i assure you, i'm making it more complicated than it should be. pete -- The mathematics [of physics] has become ever more abstract, rather than more complicated. The mind of God appears to be abstract but not complicated. He also appears to like group theory. -- Tony Zee's `Fearful Symmetry' PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
some thoughts about dosemu
hi all, just some random thoughts and questions: #1 when running redneck rampage without DPMI, the following message is printed to the xterm: lucifer# xdos kernel CPU speed is 1300264000 Hz CPU-EMU speed is 1300 MHz Running on CPU=586, FPU=1 ERROR: general protection at 0xfadf: 66 ERROR: SIGSEGV, protected insn...exiting! shouldn't dosemu catch segmentation violations and perhaps print a more useful message? or am i missing the point and dosemu IS catching a sigsegv? #2 wouldn't it make more sense to have $DOSEMU_LIB_DIR set in dosemu.conf? this file gets included into global.conf, so the global.conf should still be able to have access to whatever the user sets $DOSEMU_LIB_DIR to. #3 is there a way of getting dos to print its version number? #4 about the howto. i don't know dosemu very well, but i sure know docbook. and i would be very good about updating it. i save all the useful messages that come across this list and would be willing to put this information into the howto. the dosemu howto is one of the shortest howtos out there. it deserves to be one of the largest. ;-) can i maintain it? it's not entirely clear who has the copyright. according to license that the howto falls under, the person who is most likely the copyright holder is david hodges. but the copy distributed with dosemu is NOT the same as the copy that's on linuxdoc.org. i think that alstair is the copyright holder of the copy distributed with dosemu. we have two nearly identical documents with the same name with different copyright holders. :-) anyway, i'd promise to be a good maintainer if this is ok with people here. i contacted david hodges who said it would be ok with him. that's about it. pete -- The mathematics [of physics] has become ever more abstract, rather than more complicated. The mind of God appears to be abstract but not complicated. He also appears to like group theory. -- Tony Zee's `Fearful Symmetry' PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
dosemu howto
hi there, does anyone know if david hodges is still maintaining the dosemu howto? i'd like to add more information to it. pete -- PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D PGP Public Key: finger [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: PCI sound cards that work in dosemu?
john, if i understand bart's reply, ALL soundcards that work with linux will work with dosemu. (makes sense since app writers like bart don't handcode soundcard drivers. they use things OSS or alsa. the handcode stuff comes in when you want to *emulate* a different soundcard). the fly in the ointment isn't the card plugged into your PCI (or ISA) port. it's the soundcard the emulated application *thinks* it's using. so for instance, if your physical soundcard is the ever popular PCI-128 (works under linux) but the program you're emulating thinks it's using the little known broo-ha-ha ISA card, you're out of luck. i looked through the docs, and can't find any mention of soundcards that dosemu can emulate other than soundblaster. so unless someone says otherwise, stick with ISA soundblaster. thankfully, most DOS games knew about soundblasters. :) i think this puts you into the "trial and error mode". this should work for games that use fully compatible soundblaster cards: $_sound = (off) # sound support on/off $_sb_base = (0x220) # base IO-address (HEX) $_sb_irq = (5)# IRQ $_sb_dma = (1)# DMA channel $_sb_dsp = "/dev/dsp" # Path the sound device $_sb_mixer = "/dev/mixer" # path to the mixer control $_mpu_base = "0x330" # base address for the MPU-401 chip (HEX) # (not yet implemented) it's at least a start. hopefully, someone will correct me if i'm wrong about any of this. pete begin John C. Alden <[EMAIL PROTECTED]> > What PCI sound cards work OK within dosemu? > > I've tried the Ensoniq 1370--no luck in dosemu, though it works fine in > Linux (RH 7.2). > > I want to get sound going for a DOS-only game running under dosemu. > The Xatrix-made game lists these possibilities: > > Sound Blaster (compatible, 2.0, Pro, Pro 2.0, 16, AWE32) > Gravis Ultrasound, SoundMan 16, Pro Audio Spectrum, AWE32, Soundscape. > > Thanks for your knowledge. > > --john > > - > To unsubscribe from this list: send the line "unsubscribe linux-msdos" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D PGP Public Key: finger [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
a question about sound cards
hi all, in dosemu.conf, the soundcard section appears to imply that ISA soundblaster compatible cards are the only ones supported under dosemu, since pci users don't have to normally worry about system resources. do PCI cards like the pci 128 (es1371), ensoniq pci (es1370) and sound blaster live work under dosemu? i assume if the answer is yes, we take system resources from /proc/* and enter the resource info into dosemu.conf? pete -- PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D PGP Public Key: finger [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Permission Problem with DOSEMU
i'm a newbie myself. but i'll try to help. first, the group of "gopher" is certainly wrong. the user of "500" means that there's no user with a uid of 500. you probably just want to change everything to root.root. about the permission problem. it happens really early on. what is the contents of /etc/dosemu/dosemu.users? pete begin Gary Wynn <[EMAIL PROTECTED]> > I am having problems accessing DOSEMU to run it. A technician set it > up on my machine for me, but I cannot get it to run. Here is what I > get: > >DOSEMU will run on _this_ terminal. >To exit you need to execute 'exitemu' from within DOS, >because -C and 'exit' won't work! > >Hint: if you want $HOME as DOS drive D:, use '-home' option > >Now type ENTER to start DOSEMU or C to cancel\n > > ENTER > permission denied > > I am running RHL 7.1 on a pentium III. I am running in text mode only. > I did a chmod 777 *.* on the dosemu directory, and a chown gary.users > on that same directory. > > I get: > total 44 > drwxr-xr-x6 root root 4096 Jan 4 14:36 . > drwxr-x--- 12 root root 4096 Jan 4 14:33 .. > drwxr-xr-x2 root root 4096 Sep 18 17:18 bin > drwxr-xr-x2 root root 4096 Sep 18 17:21 conf > -rwxrwxrwx1 500 gopher 10214 Jun 2 2001 dosemu > -rwxrwxrwx1 gary users 367 Jun 10 2001 FDchange.log > drwxr-xr-x9 root root 4096 Sep 18 17:18 freedos > -rwxrwxrwx1 gary users2997 Jun 10 2001 README.bindist > lrwxrwxrwx1 500 gopher 6 Sep 18 17:18 xdosemu -> dosemu > drwxr-xr-x2 root root 4096 Sep 18 17:18 Xfonts > > I am *very* new to linux, so I do not understand why gopher appears > here. Also, I do not know why I cannot seem to change it, or how > dosemu can be run if gopher appears as the group. > > TIA > Gary > > > - > To unsubscribe from this list: send the line "unsubscribe linux-msdos" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D PGP Public Key: finger [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
making progress with the cdrom
in /etc/dosemu/dosemu.conf: $_aspi = "sr0:CD-ROM" in /usr/lib/freedos/config.sys: devicehigh=c:\dosemu\cdrom.sys in /usr/lib/freedos/autoexec.bat: mscdex /d:mscd0001 /l:E here's the problem. freedos doesn't provide mscdex. i saw a reference to something called fdcdex, but that's not on my system either. can someone please help me? pete -- PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D PGP Public Key: finger [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
how to get a scsi cdrom working
hi there, i have a plextor scsi cdrom, /dev/sr0. how do i get it to work under dosemu? there appears to be no mscdex.exe on my system (i'm using freedos). would i really refer to the drive as sg0 (as dosemu.conf says) as opposed to sr0? thanks! pete -- PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D PGP Public Key: finger [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
