Date: Sun, 29 Dec 91 23:11:11 PST Message-Id: <17644@n6paw.ampr.org> From: gary@n6paw.ampr.org (Gary D. Evans) Reply-To: gary@n6paw To: larry%n6sle@kg6kf Subject: DesqView Info for NOS and BM Hi Larry, It took me a little longer to get to the building of this file but it includes everything you should need to get nos and bm up and running in their own windows. As is stated in the file, to use qemm386 you need a 386 or 486 class machine. I don't have any info on 286 or XT machines at the moment. Good luck. [...] 73's, -- Gary ---------------------- Documentation File Follows ---------------------------- The following was found to work correctly on a 486-33 with 4 megabytes of RAM running DOS 5.0 with Quarterdeck's qemm386 package (memory manager version 6.0). Included are the config.sys and autoexec.bat files used here currently. ----------------------------------------------------------------------------- ------------------------------------------------------------------------------ My config.sys file ------------------------------------------------------------------------------ files= 30 rem device=C:\himem.sys device=c:\qemm\qemm386.sys r:2 ram ST:M dos=high DEVICE=c:\qemm\loadhi.sys /r:1 c:\mouse\mouse501.sys DEVICE=c:\qemm\loadhi.sys /r:1 c:\dos\nansi.sys DEVICE=c:\qemm\loadhi.sys /r:1 c:\dos\setver.exe DEVICE=c:\qemm\loadhi.sys /r:1 c:\dos\ramdrive.sys 1024 512 64 /e DEVICE=c:\nort\ncache.exe /INSTALL /EXP=2048K /QUICK=ON C:/+I SHELL=C:\NORT\NDOS.COM c:\nort /e:512u /S:B /U /P BUFFERS=40 lastdrive=d stacks=0,0 ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ My autoexec.bat file ------------------------------------------------------------------------------ @echo off PATH C:\QEMM;A rem PATH A resets the path to be re-reset at end of autoexec.bat c:\nort\ncc nccdef/setall c:\nort\ncc nccdef/cursor C:\QEMM\LOADHI /R:1 FILES=30 c:\qemm\loadhi /r:1 lastdrive=+18 c:\dos\subst f: c:\space\traksat c:\dos\subst i: c:\paradox3 c:\dos\subst m: c:\packet\spool\mqueue c:\dos\subst n: c:\srcfiles\nos c:\dos\subst p: c:\packet c:\dos\subst s: c:\srcfiles c:\dos\subst t: c:\phone c:\dos\subst u: c:\uupc set TEMP=d:\ set TMP=c:\packet\tmp set LIB=c:\unix\lib set TZ=PDT7 set PCPLUS=c:\pcm set DIRCMD=/oge/l d: md tmp c: break on PATH c:\qemm;C:\dos;C:\unix;C:\;C:\Bat;C:\Util;C:\Ws;C:\Nort;e:\;c:\Bc\bin;c:\Pcm;U:\Bin;U:\Bat;C:\Util\Shez;P:\;C:\Paradox3;C:\Windows;c:\virus prompt $p$g FR /SAVE cls ------------------------------------------------------------------------------ TO INSTALL NOS (GRINOS v1.7j) ----------------------------- In "change program" window #1: Program Name: NOS Keys to Use : NO Memory Size : 585 Program... : p:\n.bat Parameters : Directory. : p:\ Options: Writes text directly to screen ...............: [N] Displays graphics information ................: [N] Virtualize text/graphics (Y,N,T) .............: [N] Uses serial ports (Y,N,1,2) ..................: [2] Requires floppy diskette .....................: [N] In "change program" window #2: System Memory ..................................: 0 Maximum Program Memory Size ....................: Script Buffer Size .............................:1000 Maximum Expanded Memory Size ...................: Text Pages : 1 Graphics Pages : 1 Initial Mode : Interrupts : 00 to FF Window Position : Maximum Height : 25 Maximum Width : 80 Starting Height : Starting Width : Starting Row : Starting Column : Shared Program Pathname : Data : Close on exit (Y,N,blank) ......................: [Y] Uses its own colors ............................: [N] Allows Close Window command ....................: [Y] Runs in background (Y,N,blank) .................: [Y] Uses math coprocessor ..........................: [N] Keyboard conflict (0-F) ........................: [0] Share CPU when foreground ......................: [Y] Share EGA when foreground/zoomed ...............: [Y] Can be swapped out (Y,N,blank) .................: [N] Protection level (0-3) .........................: [0] ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ TO INSTALL BMailer ------------------ In "change program" window #1: Program Name: B.Mailer Keys to Use : BM Memory Size : 400 Program... : p:\bm Parameters : Directory. : p:\ Options: Writes text directly to screen ...............: [N] Displays graphics information ................: [N] Virtualize text/graphics (Y,N,T) .............: [N] Uses serial ports (Y,N,1,2) ..................: [N] Requires floppy diskette .....................: [N] In "change program" window #2: System Memory ..................................: 0 Maximum Program Memory Size ....................: 600 Script Buffer Size .............................:1000 Maximum Expanded Memory Size ...................: Text Pages : 2 Graphics Pages : 0 Initial Mode : Interrupts : 00 to FF Window Position : Maximum Height : 25 Maximum Width : 80 Starting Height : Starting Width : Starting Row : Starting Column : Shared Program Pathname : Data : Close on exit (Y,N,blank) ......................: [Y] Uses its own colors ............................: [N] Allows Close Window command ....................: [Y] Runs in background (Y,N,blank) .................: [Y] Uses math coprocessor ..........................: [N] Keyboard conflict (0-F) ........................: [0] Share CPU when foreground ......................: [Y] Share EGA when foreground/zoomed ...............: [Y] Can be swapped out (Y,N,blank) .................: [Y] Protection level (0-3) .........................: [0] ------------------------------------------------------------------------------ --------------------------- End of File -------------------------------------- -- *-------------------------------------------------------------* | N gary%n6paw@n6ng | | W -|- E gary%n6paw@kg6kf -|- gary%n6paw@hisac | | S gary%n6paw@aa6iw | *-------------------------------------------------------------* From tcp-request@noe Wed Jan 22 13:57:07 1992 Date: Sun, 19 Jan 92 14:13:23 EST From: "Bob Austin" To: TCP-Group@UCSD.Edu Subject: mailbox and DV Mike, why would you want to shell out of nos, if you are running DV? I just created another window, and run the mbox from there. that way I dont get nos to shell out for anything. I even turned multitask off. Since DV will take care of the multitasking, my thought was to keep it simple.? 73, => Bob - N4CLH @ KK4L.NY.USA.NA or WF2A.NY.USA.NA => amprnet - 44.69.0.75 (n4clh.ampr.org) via KK4L-1 in Binghamton, NY => internet - rwaustin@gdlvm2.vnet.ibm.com From tcp-request@noe Mon Feb 24 06:33:27 1992 Sender: Date: Mon, 24 Feb 1992 02:44:23 EST From: "Mike Bilow, mikebw@ids.jvnc.net" To: bill@tuatara.uofs.edu Cc: tcp-group@ucsd.edu, mikebw@IDS.JVNC.NET Message-Id: <009569DB.6AD53640.24177@IDS.JVNC.NET> Subject: RE: TABS in NOS It may be all right to say "Get rid of ANSI.SYS and use NANSI.SYS," but a lot of people run NOS under DesqView, where you must use DVANSI.SYS to have it active within the DV windows. There is a public domain DVNANSI.SYS, which also disables keyboard remapping, but I am not sure if this expands tabs or not. (I am not using it here, although I do have it.) (Let me correct all references to DVANSI.SYS or DVNANSI.SYS; I mean DVANSI.COM and DVNANSI.COM.) Also, tabs are not little smiley faces. Tabs are little bullets in the IBM extended character set. -- Mike Bilow, (Internet) From tcp-request@noe Wed Mar 18 04:40:41 1992 Date: Tue, 17 Mar 92 15:09:52 PST From: "Jerzy Tarasiuk" Message-Id: <454.JT@zfja-gate.fuw.edu.pl> To: "Thomas Nilsson, KI/ERA/R/LRLC, Sweden" Cc: tcp-group@ucsd.edu Subject: Re: NOS & DV > I am still curious about why it doesn't work if you load the hardware driver > inside a DV window. It is more or less stated in the manual for DV that it > should work. There is a problem of hardware interrupt servicing in multi-tasker like DV: which task should receive the interrupt ? I suppose active task can receive the interrupt if vector was set by it; "active" may mean either "actually using CPU" or "foreground" - I don't remember which of these. Possibly good strategy is interrupt each task which has set interrupt vector (and not restored to original value), but this either was not implemented in DV or we don't know how enable it. It is also possible DV itself receives data from serial port and is not smart enough to know there is a program which needs it. -JT