Hi Linda,

 LP> Got it installed on the clunker.

See... the earth isn't falling.......;-)


 LP> Well won't do anything DOS or Win-OS,

First, to make sure we are all talking the same language, what version of OS/2 
are you installing, EG: Warp 3 Connect RED spine...

Ok, some questions before we start on this -
 - In what way "it wont do" DOS (we need some more details)? 
 - Do you have a "DOS Window" Icon in the COMMAND PROMPTS folder? 
 - What happens when you double click/select & ENTER it?
 - What is the size of the partition that OS/2 installed to?
 - Is it FAT or HPFS?
 - How much FREE disk space does it have?
 - If you are really game, try posting the contents of your CONFIG.SYS here so 
we can see what your installation looks like, it may provide some very useful
clues for any issues you have.


 JP> and won't read the DOS C drive 

If you are using multiple primary partitions then that is not surprising.


 LP> but has assigned it's own drive as C (in order to install).  

This is the "protective" mode of OS/2, it only tries to work with what it
knows or the user confirms can be done, it does not try and mussle its way in
unlike some other OS's.


 LP> Lost my inport mouse 

It probably can't autodetect one of those, you may need to go into System
Setup ==> Selective Install and manually configure the type of mouse. I had
the same problem here with a Logitec BUS mouse, it did not autodetect, but I
was able to manually configure it from a list of possible types of mouse that
it could not detect it and it worked great.


 LP> & hung playing a game.  

What "hung"? In many cases a system that does not respond to keystrokes
immediately has not "hung", it could be running fine, its just the user
keyboard interface is being locked by a badly behaving application. The WORST
thing to do at this time is to pound the keyboard! All that does is fill up
the keyboard buffer.

While it is not impossible to "hang" OS/2 from a DOS session, OS/2 often
manages to grab control back from something that tries to take liberties with
the system, but this can take _T_I_M_E_ and a response is not always
immediate. 

Also try CTRL-ESC and ALT-ESC, but after pressing either of these WAIT for 20
seconds for a response. A later fixpak for Warp 3 added a facilty to better
manage what is called "Single Input Queue" lockups. While not essential, it
became a standard feature in Warp 4.

There are many special DOS Settings that can be used to try and "tame" a
rampant DOS application, the default settings are normally ok to get things
working, however I normally modify either the standard "DOS Window" settings
to add specific settings I want or create a new Icon and use that Icon as the
mould for all subsequent DOS sessions that I need. 


 LP> And want to see the DOS C.  

I suspect your partitions are configured in a manner that will not allow this
under OS/2. I am picking that if you really do have multiple primary
partitions on that drive, then you really are up the creek without a paddle,
however some of the other folks here may be able to provide a few tricks to
resolve this.


 LP> And it doesn't have an Epson FX-80 printer driver.

While not specifically for the FX-80, there is another Epson printer which is
almost identical to the FX-80 that is there, but I can't remember which one it 
is.  Its been MANY years since I used a Dot Matrix.

Start with the "Epson Generic 9 pin" driver for the FX-80 and checkout the
other Epson printers, the FX-80 was rebadged under another name for other
parts of the world. If you do not have a printer object, go into System setup
==> Selective install, and check out the list of Epson printers, and am sure
you willfind one that will work, dot matrix printers generally have a generic
mode of operating so something should work fine.


 LP> But then it only has 6 MB 

That should have no affect on the issues you have seen. It will inhibit some
things, but it should still run (walk.....;-)).


 LP> & I admit I did not try to make the swap file on the 3rd partition.

Provided the OS/2 install partition has enough space to expand the swap file
to whatever size it needs, this should not cause any of these problems. Moving 
the swap file for performance reasons should be a minor issue...

TIP: If you change the location of the SWAP file, make sure that after
re-booting using the NEW loaction, you DELETE the OLD swap file to regain the
disk space it used!


 LP> And it has the old bios.

And that is TOTALLY out of the picture now that OS/2 has booted. Forget it!


 LP> Multiboot works fine, though.

At least thats ONE positive sign......;-)


I hope some of this helps........pk.

--- Maximus/2 3.01