TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: John R. Wainwright 72517,676 (X)
from: Ed Gresick 76576,3312
date: 1995-06-25 05:10:37
subject: #21016-#OS-9000 help

#: 21020 S12/OS9/68000 (OSK)
    25-Jun-95  05:10:37
Sb: #21016-#OS-9000 help
Fm: Ed Gresick 76576,3312
To: John R. Wainwright 72517,676 (X)

 John,

 Congratulations on getting OS9000 up and running.  Which version are you
 running?  Using the release sold at the CocoFest in Chicago a few years ago
 *may* account for some of your problems.  As I recollect, there were many
 bugs in it.  The latest version is 1.3. - much smoother.  I think its worth
 spending $200 per year for the support contract.  In addition to hotline
 support, you should be able to get the latest version of OS9000 as part of
 the package.  The people at MW say version 2.0 should be released in the
 next couple of months.

 > 1. Comm ports.  I can use T1 and T2.  Even had STERM talking to CIS when I
 > had the (internal) modem on T2 (COM2).  Then I moved the modem to T4
 > (COM4).  T2 is now a simple serial port.  T2 still works, I can plug it
 > into an external modem or null-modem to the MM/1, but I cannot get OS-9000
 > to talk to T4.  Messydos & Windoze and even OS/2 can find that modem, but
 > OS-9000 cannot.  COM2 and COM4 are BOTH using IRQ3, but I am not trying to
 > use them at the same time.

 If MSDOS, etc. can find and speak to the modem correctly, its safe to say you
 have the card configured correctly.  Check the data for the descriptor to
 be sure it matches your modem configuration.  This information is stored
 in '/dd/PORTS/PCAT/systype.h'.  Use '/dd/PORTS/PCAT/mk.scfdesc' to make a
 new descriptor.  BTW, I use an internal modem on t3 - no problems.

 > 2. Printer.  I am using LPT1.  The address of the port seems right
 > accord to the BIOS and the information with the OS-9000 system.
 > It even makes the lights blink and puts the Deskjet through its
 > INIT routine when I load and init p.lpt1.  When I try to print
 > something, the lights blink on the printer and the system hangs.
 > LPT1 works fine with the other operating systems, of course.
 > Current method of printing from OS-9000 is to pass it via null
 > modem to the MM/1.

 Don't have any suggestions for this one.  I've had no problems.  Currently,
 I'm using either an old OKI 192 or a HP 4+.  Both work fine.  You might
 try calling MW's hotline.

 > 3. Disk formats.  No big deal here, but I sure can't get the MM/1
 > and the OS-9000 system to agree on what a "universal disk" is.  I
 > CAN get them both to read and write on a High density messydos
 > disk, so I use that for transfers.

 OS-9/68000 and OS9000 'universal formats' are not the same.  If I remember
 correctly, the main difference is where the FAT is placed.  Using 'os9copy'
 or 'os9dsave' located in the '/dd/CMDS/UNSUPPORTED' directory, you should
 be able to read OS-9/68000 universal format disks.  Otherwise, you're doing
 what most of us are doing - transferring via MSDOS disks or via the serial
 port.

 > 4. Graphics.  Anything available to get OS-9000 to speak to the
 > Trident 94xx VGA card in this beast?  I need a CGFX_VGA.L  lib
 > (grin).

 Well, I have G-WINDOWS for OS9000.  Have 2 drivers that should work with your
 card'.  These are generic drivers giving a resolution of 640x480x16.  I have
 additional drivers for specific cards (the Trident isn't included) providing
 resolutions up to 1200x1024x256.  With the  optional Developer's Pak, you
 have what you need to write software for gfx using G-WINDOWS.  Alternatively,
 you can purchase RAVE.  I don't think there is a driver for the Trident cards,
 but a skeleton driver is included you can fill in to make your own driver.

 Ed

There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.