TIP: Click on subject to list as thread! ANSI
echo: os2
to: Linda Proulx
from: Peter Knapper
date: 1999-11-16 22:26:03
subject: Re: Clunker update

Hi Linda,


 LP> Reinstalled the WIN. Voila working.

Great...


 PK>  - Is it FAT or HPFS?

 LP> HPFS.  Put the swap on D FAT 16.

Uhg....FAT!..;-( You have possibly just destroyed any gain you had by placing
it on another drive. The Swap file performs best when -
 - It can be QUICKLY accessed!
 - It is written as ONE CONTIGUOUS AREA of disk. 

HPFS is excellent for a SWAP file because space is allocated in bands, so
files that expand in size are nearly always contiguous. FAT is just about the
worst place to store a Swap file, because FAT fragments so easily (unless you
force a pre-allocated Swap file of a fixed size on a recently compressed
partition). Put it back on the C: (HPFS) drive.... NOW!.......;-)


 PK>  - How much FREE disk space does it have?

 LP> Sorry forgot.

As long as your C: drive has plenty of room (say 100Mb BEFORE your SWAP file
is placed there) you should be fine.


 JP> and won't read the DOS C drive

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

 LP> In multiboot says it's hidden.  How do I change this with the Fdisk.  D
 LP> is fine.

I dont know Multi-boot so others can probably handle this better. I suspect
you may have to turn some of those Primary partitions back into Logical drives 
to do what you want........;-(


 LP> Lost my inport mouse

 PK> It probably can't autodetect one of those, you may need to go into

 LP> It auto detected but it keeps disappearing & had to use the keyboard
 LP> to load down.  That is a real oucher.  Mine is an MS Buss mouse.

Ahaaaa. If the MOUSE is disappearing after/while running a DOS/Win session,
then you may need to investigate the DOS settings for that session and check
out the settings that relate to the MOUSE. Sometimes DOS programs have the
mouse driver code built-in, because a MOUSE is not always standard under DOS.
When those applications run in a DOS box under OS/2, they are prevented from
talking directly to the mouse, so you may need to "tweak" a DOS setting to
allow that specific application direct access. 

Caution: Sometimes this can be a rocky ride if the application fiddles with
the mouse settings that then take affect in ALL other OS/2 (or other DOS)
windows... You may need to play with this a bit to get it working ok, it
really depends on WHAT the DOS S/W does to the mouse. Either way you should be 
able to get something working.


 LP> & hung playing a game.

 PK> What "hung"? In many cases a system that does not 
 PK> respond to keystrokes

 LP> Oh, it hangs.  C-A-D won't even work.  Little reboot button time.

If this is also a DOS application, then you need to investigate the DOS
settings. This one is tricky, there are a LOT of options and a slight change
on one of them is all that may be needed to resolve this problem. Post details 
of the specific application and someone may be able to suggest some known
settings.

Have a browse around the DOS Settings, you will find a LOT of options
availabe. Many of these allows you to tweak that specific application and
these often can work wonders. If you need more help, then it would cetainly
pay to indicate what the application name is (IE what the executable filename
is).


 LP> And want to see the DOS C.

 LP> During the Fdisk I didn't want to play with the DOS C.  I think I
 LP> assigned it as bootable but can't remember at the moment.

 PK> primary partitions on that drive, then you really are up the creek
 PK> without a paddle, however some of the other folks here may be able to
 PK> provide a few tricks to resolve this.

 LP> I think Fdisk will fix this.  After all I'm using Drive D.  Just ansy
 LP> about playing with the DOS partition at the moment.

I am now confused, I though you had OS/2 installed to drive C!!! If OS/2 is on 
D:, then what partition is OS/2 seeing as C: ??? 

Remember, if you quote drive letters, make sure everyone understands what OS
you have booted that sees them as those letters, and if relevant, also
indicate how OS/2 sees them when its running... 


 LP> But then it only has 6 MB

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

 LP> Stutter?

Only if you try and run too fast.......;-) At least you have a road to head
down now, just watch out for the pot-holes. 6MB is not a lot of memory, so
things will not be fast, and dont open up too many windows just yet. Once you
get a better feeling for how things are running you can tweak these and can
end up with better settings for each of your DOS sessions, but it will take
time and understanding to work it all out.

BTW: What is the processor in that machine anyway? 

Cheers..........pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

SOURCE: echoes via The OS/2 BBS

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™.