--------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4Q00000 Date: 04/04/97 From: JOE CARTER Time: 11:29am \/To: WAYNE SIEMUND (Read 2 times) Subj: Re: Real Audio On 30 Mar 97 13:41:14, Wayne Siemund was talking to James Mckenzie WS> I figured it out. WS> I got rid of that RAGO.CMD and just told Netscape to run RAPLAYER.EXE WS> with the %S perameter. I found I have to close RA before trying WS> another site to listen to or produces an error window and closes WS> netscape. OS/2 apparently detects a windows program and starts is WS> appropriatly. My first test was with the Art Bell Show. the audio was WS> ok and interupted a bit with interesting phase-shifting, but quite WS> understandable. Perhaps off-peak time would present better results. WS> B-) Cool! I have been toying with it myself and watching this thread. I too listen to Art Bell when I can stay up and that's not often, so I am VERY interested in RA working. Interesting coinkydink that happened to be your first test. Hale to the end of the age. ~~~ ReneWave v2.00 [NR] --- Renegade Forever! * Origin: Kaat's Keep / Salem, OR USA / 503-375-0567 (1:3406/7) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4Q00001 Date: 04/05/97 From: JOE CARTER Time: 01:05pm \/To: JUSTIN BAUSTERT (Read 2 times) Subj: Re: os/2 under WinNT? On 04 Apr 97 07:52:32, Justin Baustert was talking to Assaf Shool AS> Is it possible to run os/2 apps under WInnt4? I was looking through AS> it and it looks like some of the programs in it belong to os/2 AS> aswell as some os/2 files are in there as well. Has anybody tried AS> running os/2 pm apps under NT??? JB> I asked a similar question some time ago in one of the comp.os.os2.* JB> newsgroups.. The only OS/2 programs that NT can run are text-mode JB> 16bit apps.. PM apps won't work.. All the more reason to run OS/2, right? ~~~ ReneWave v2.00 [NR] --- Renegade Forever! * Origin: Kaat's Keep / Salem, OR USA / 503-375-0567 (1:3406/7) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4Q00002 Date: 04/09/97 From: JOE CARTER Time: 03:41pm \/To: WALTER METCALF (Read 2 times) Subj: Re: Sound Under Warp On 05 Apr 97 14:03:00, Walter Metcalf was talking to Joe Carter WM> Has anyone figured out how to get the microphone port on the Sound WM> Card towork after a sound-enabled Win-OS/2 system has been opened a WM> closed? The result is that once the Win-OS/2 has been (and closed) WM> Voice Manager is killed/disabled until the system is rebooted. WM> I've tried 3 different sound-cards to no avail. I'm about to try WM> another, but I keep thinking there must be a patch or short batch file WM> I could write to reset that blasted port. There's a buggy seamless.dll in Warp4 that might be the cause of this. FP1 has it and Netscape 2.02 does as well.. You can unpack the old one, though someone would have to give you the exact command as I can't. It's in disk image 5 on the CD-ROM. ~~~ ReneWave v2.00 [NR] --- Renegade Forever! * Origin: Kaat's Keep / Salem, OR USA / 503-375-0567 (1:3406/7) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4Q00003 Date: 04/10/97 From: JOE CARTER Time: 03:27am \/To: TONY LANGDON (Read 2 times) Subj: Re: os/2 under WinNT? On 06 Apr 97 02:54:36, Tony Langdon was talking to Assaf Shool [Only works with 16 bit OS/2 apps] TL> I don't have any other 16 bit applications to try out. :-( There's a patch for BP7 that will make 16 bit OS/2 EXE's instead of 16 bit DOS EXE's.. ~~~ ReneWave v2.00 [NR] --- Renegade Forever! * Origin: Kaat's Keep / Salem, OR USA / 503-375-0567 (1:3406/7) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4Q00004 Date: 04/13/97 From: JOE CARTER Time: 04:41pm \/To: BRENT SMITH (Read 2 times) Subj: Re: Renegade prob, on os/2 network drive16:41:3104/13/97 On 13 Apr 97 01:25:12, Brent Smith was talking to Jonathan De Boyne Pollard JD> BS> I've recently added a network to my bbs computer, and made my d drive JD> BS> into a network drive p: [...] JD> JD> BS> but a couple times a day i get a error writing to network drive JD> BS> p:\renegade\data\ [...] JD> JD> What sort of LAN software is this (OS/2 Peer ? LANTastic for OS/2 ?), and JD> what is displaying the error message (the BBS software ? the hard error JD> daemon on your fileserver ? the hard error daemond on your client JD> workstations ?) ? BS> os/2 built in lan using ethernet cards, happens on the server, when no BS> other sytems are connected, and os/2 is giving me the error... Waaaaaaitasec... For my "server" to work with the BBS, I must set the drive mappings on it as well. Keep, my main machine does nodes 1 and 2, Node3 is, naturally node 3. On node3, I have the drives mapped with WFW: q: --> \\keep\c r: --> \\keep\d s: --> \\keep\e t: --> \\keep\f Now, startup.cmd on keep: @ECHO OFF CALL C:\IBMLAN\NETPROG\NETSTCMD.CMD START PEER CALL C:\TCPIP\BIN\TCPSTART.CMD C:\MUGLIB\LOGON.EXE KNGHTBRD /P:[notachance!!] C:\IBMLAN\NETPROG\NET.EXE USE Q: \\KEEP\C C:\IBMLAN\NETPROG\NET.EXE USE R: \\KEEP\D C:\IBMLAN\NETPROG\NET.EXE USE S: \\KEEP\E C:\IBMLAN\NETPROG\NET.EXE USE T: \\KEEP\F EXIT I don't use network messaging and I can probably also assume I don't need tcpstart.cmd but it seems to be harmless so I keep it there. You probably need to be logged on to the system to map the drives, it's best to use the logon line above as I did. We have no need of any sort of network security here so I just log myself on. The danger here is the possibility that someone on the BBS might get to a DOS or OS/2 command shell. And that's a real threat. Figure that if they get access to your sysop menu, you're good as dead. Minidos, edit a cmd file, then ext start same... The point is to not let them get there. JD> You would probably find more help if you ask in the OS2LAN echo, JD> incidentally. This is the OS2DOS echo, where we discuss DOS and DOS+Window JD> software running under OS/2. The OS2LAN echo is for discussing netework JD> problems. BS> didnt know there was a os2lan echo... BS> and the bbs is in a dos box, dont know if its a lan error or a dos BS> error areafix OS2LAN and if you don't have it also OS2BBS. If something I have suggested here based on my setup helps any, that's cool by me. => ~~~ ReneWave v2.00 [NR] --- Renegade Forever! * Origin: Kaat's Keep / Salem, OR USA / 503-375-0567 (1:3406/7) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4Q00005 Date: 04/19/97 From: GLENN THOMPSON Time: 01:44pm \/To: ALL (Read 2 times) Subj: W4 Dos support Hi All, Am having difficulty with warp4 and ansi screens in a dos session. On text boxes things like corners and such are not displayed correctly, I generally see some kind of letter instead. The letter usually appears to be from the high end of the ansi table. This is especially noticable during a dos BBS session. Dos programs eg;Bluewave, Borland C 3.1, are unusually slow as well Any ideas will be appreciated thanks. Glenn. ... A feature is a bug with seniority. --- Blue Wave/Max v2.20 [NR] * Origin: Ground Zero BBS - 61 8 8325 1822 SouthNet Mail Host (3:800/409) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4Q00006 Date: 04/20/97 From: DAVID NOON Time: 06:44pm \/To: STEPHEN HAFFLY (Read 2 times) Subj: VMB image creation On Friday, 97/04/18, Stephen Haffly wrote to David Noon about "Dedicated Dos" as follows: SH> DN> I use this approach for both PC-DOS 6.3 and PC-DOS 7.0 sessions run SH> DN> from image files on a HPFS partition. These sessions can access all [snip] SH> Even if he doesn't, I do. Please post the details. Hi Stephen, Creating a specific DOS image is quite simple, except that you need a bootable copy of the DOS release to start the process. The best floppy disks to use are 720KB ones, or even 360KB, since the image file is as large as the floppy, even if most of the floppy is free space. 1) Boot a copy of "DOS X" and format a floppy disk with the /S option. 2) Boot your OS/2 system. 3) From your x:\OS2\MDOS directory, copy EMM386.SYS, HIMEM.SYS, FSFILTER.SYS and FSACCESS.EXE to the root directory of the floppy disk. 4) Create a CONFIG.SYS file in the root of the floppy with the following (as a minimum): DOS=HIGH,UMB DEVICE=A:\HIMEM.SYS DEVICE=A:\EMM386.SYS DEVICEHIGH=A:\FSFILTER.SYS DEVICEHIGH=x:\OS2\MDOS\ANSI.SYS [Only if you want ANSI screen stuff] 5) Create an AUTOEXEC.BAT in the root of the floppy with the following (as a minimum): VERIFY OFF PATH A:\;x:\OS2\MDOS;x:\OS2 LH APPEND x:\OS2\MDOS;x:\OS2 LH DOSKEY EXIT=EXIT_VDM $* In both the CONFIG.SYS and the AUTOEXEC.BAT, the A: drive letter should be coded exactly as above, even if the FDD you are using for it is actually B:. This is because the image file will always be A: at run time. 6) [Optional, as testing always is] Test the floppy image using the "DOS from A:" icon in the Command Prompts folder, inside your OS/2 System folder. If your FDD is B: you will need to fiddle with the session's settings notebook to make it boot its A: image from physical B:, but that's fairly easy: adjust the DOS_STARTUP_DRIVE setting. Fix any problems; that's not always easy. 7) When finished testing, create an image file by running VMDISK a: z:\dosdir\dosboot.vmb, where the first parameter is the FDD from which to read the bootable diskette and the second parameter is any valid path/filename 8) Drag an drop a program template from the system templates folder. Give it a program name of *, a working directory of wherever you left the image file from step #7, and a session type of DOS Full-screen or DOS Windowed. Set the DOS_STARTUP_DRIVE to the path/filename of the image file. Adjust the memory settings for XMS, EMS and/or DPMI, as needed. Thereafter, you just double click on the icon created in step #8 whenever you want that specific version of DOS. The main "gotchas" are: EMM386.SYS doesn't like it when you set the EMS_MEMORY_LIMIT to zero. REM the DEVICE line out of CONFIG.SYS too, to swith off EMS. You cannot readily access the real A: drive from the VMB session. You can use FSACCESS to assign it a later letter, such as FSACCESS K=A, which will make it the K: drive in the VMB. Unfortunately, COMMAND.COM doesn't always pick up dynamically added drives, so you sometimes need to run DOSSHELL or the like after the FSACCESS to access the FDD. Regards Dave * KWQ/2 1.2i * Darwin stubby -- truly the survival of the fittest. --- Maximus/2 3.01 * Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4S00000 Date: 04/19/97 From: FRED SPRINGFIELD Time: 01:39pm \/To: ALL (Read 2 times) Subj: 736K DOS It was probably discussed a long time ago--but how do I do it with Warp 3 (blue)? I have tried setting VIDEO MODE RESTRICTION to CGA, setting DOS RMSIZE to 636 (there is a bug at 640 and this is the workaround), and messing with the other DOS settings, BUT I cannot get MEM up over 655K. Does anyone have the answer on how to do this? TIA Fred --- * KWQ/2 1.2i * Hope alone won't get you there-try adding some work. --- WILDMAIL!/WC v4.12 * Origin: The Warehouse BBS (612) 767-2966 (1:282/115.0) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4S00001 Date: 04/22/97 From: MORRIS TURPIN Time: 05:02pm \/To: FRED SPRINGFIELD (Read 2 times) Subj: 736K DOS Hello Fred, In a message dated Apr 19 at 13:39, Fred Springfield of 1:282/115 wrote to All: FS> I have tried setting VIDEO MODE RESTRICTION to CGA, setting FS> DOS RMSIZE to 636 (there is a bug at 640 and this is the FS> workaround), FS> and messing with the other DOS settings, BUT I cannot get MEM up FS> over 655K. FS> Does anyone have the answer on how to do this? Are you using Disk Manager (or one of its OEM variants) on your hard drive? If you are then you won't be able to get DOS sessions above 640K because it loads itself at the top of the 640K boundary. Morris Turpin Proud Member of Team OS/2 fidonet: 1:163/140.3 internet: mturpin@igs.net --- msged 2.07 * Origin: Warped in Ottawa, Canada (1:163/140.3) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E4S00002 Date: 04/22/97 From: JOCELYN DOIRE Time: 07:04pm \/To: FRED SPRINGFIELD (Read 2 times) Subj: 736k Dos Hello Fred, FS> I have tried setting VIDEO MODE RESTRICTION to CGA, setting FS> DOS RMSIZE to 636 (there is a bug at 640 and this is the FS> workaround), and messing with the other DOS settings, BUT I FS> cannot get MEM up over 655K. Do you have "Disk Manager" or "Ontrack" installed on your machine? It shows up when you start, allowing you to boot from a floppy instead. If you do, then you can not get more than 640k, because the program lives at the top of the 640k, and block access to above memory. The only only way to fix that, is to remove it, which means a re-format of the hard disk. In my case, I found out that I did not need it after all. Joc ___ X KWQ/2 1.2i X "640K ought to be enough for anybody." - Bill Gates, 1981 --- Maximus/2 2.02 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)