🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: aus.computers.os2
Article #6858

Re: WinOS2 and the MACH64

#6858
From: John Leonard
Date: Fri, 17 Feb 1995 11:45
96 lines
4298 bytes
In <3i0kud$qg1@nic.umass.edu>, rll@titan.oit.umass.edu (Robert L Layton) writes:
>Marvin R McCreary (mmccrear@magnus.acs.ohio-state.edu) wrote:
>: In article <3hm7ao$so2@sunb.ocs.mq.edu.au>,
>: Mark Krischer  <mkrisch@mpce.mq.edu.au> wrote:
>: >thanks to everybody's suggestions.
>: >    osborne technical support said i should exclude memory
>: >    regions a000-cfff, i'll be trying that tonight.  it sounds
>: >    like the best solution i've heard so far. so, for those that
>: >    have a similar problem, you might give this a try.
>: >
>: >thanks again
>: >
>: >mark
>: How do you do that?
>
>: Marvin
>are you guys all going loony, I have a mach64 card and it is working 
>beutifully in win-os2
>Rob

I am also running a Mach64 on a Dell P5100.  No problems on the install
at all.  Warp went up the first time.

I have noticed (during install problems of a Mach8 card) that sometimes
old driver names are left in the SYSTEM.INI.  Thus, the wrong
WinOS/2 drivers are used.  This results in funny WinOS/2 performance including
machine locks ups and stalls, "scrunched" displays, and other hideous
display problems.  IMHO, the simplest fix is to:

1) Uninstall WinOS/2 support. (Selective Uninstall)
2) Boot under DOS and completely reinstall Windows.  This will ensure that
   the SYSTEM.INI and the WINDOWS\SYSTEM directories are clean.  At this time,
   set up the ATI drivers for the correct resolution (it doesn't matter when
   you do this, but I have found it cleaner to have a completely stable
   version of Windows before I jump to OS/2.  I also ensure that the audio
   is stable. (Again, not pertinent to your problem specifically, but cleaner
   in the long run.
3) Reinstall WINOS2 support.  Pick the Mach64 chipset. (Selective Install)

I have had NO need to perform any funny memory exclude stuff.  THAT IS NOT
YOUR PROBLEM!

What follows are selected sections from my SYSTEM.INI.  Check that your
SYSTEM.INI has these settings.  I think that the key driver names
are fdisplay.drv and sdisplay.drv in the [boot] section.

[boot]
os2mouse.drv=mouse.drv
atm.system.drv=system.drv
useos2shield=1
os2shield=winsheld.exe
os2fonts.fon=8514sys.fon
fdisplay.drv=fmacx.drv
sdisplay.drv=smacx.drv
MAVDMApps=

[boot.description]
displayinf=OEMMACX.INF
keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards
mouse.drv=Microsoft Mouse version 9.01
network.drv=No Network Installed
language.dll=English (American)
system.drv=MS-DOS System
codepage=437
woafont.fon=English (437)
aspect=100,120,120
display.drv=ATI mach64: 1024x768x65k (Large Font)
fdisplay.drv=ATI
sdisplay.drv=ATI

[386Enh]
device=C:\WINDOWS\SYSTEM\WIN32S\W32S.386
device=dva.386
device=vsbpd.386
COM3FIFO=2
COM3Buffer=1024
COMBoostTime=20
device=c:\dos\vfintd.386
32BitDiskAccess=OFF
device=*int13
device=*wdctrl
mouse=*vmd
network=*dosnet,*vnetbios
ebios=*ebios
woafont=dosapp.fon
display=macxvdd.386


Sorry about the length of the message, but I hope that it helps.

JL
-----
John D. Leonard II, Assistant Professor              Phone: 404/894-2360
School of Civil and Environmental Engineering          FAX: 404/894-1742
Georgia Institute of Technology               john.leonard@ce.gatech.edu
Atlanta, GA  30332-0355                 http://civilstat79.ce.gatech.edu
Technical Details
Message-ID: <3i229c$iqn@mordred.gatech.edu>
Path: arc1-ca.pugleaf.net!nntp.gmd.de!newsserver.jvnc.net!news.cac.psu.edu!news.pop.psu.edu!ra.nrl.navy.mil!cs.umd.edu!zombie.ncsc.mil!news.mathworks.com!udel!gatech!gt-news!news
References: <3hcbc5$cn4@sunb.ocs.mq.edu.au> <3hkajr$c9h@charm.magnus.acs.ohio-s <3hpq5j$84@charm.magnus.acs.ohio-state.edu> <3i0kud$qg1@nic.umass.edu>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10a752,6c4be0182744c447
X-Google-Attributes: gid10a752,public
X-Google-Thread: 107fbf,6c4be0182744c447
X-Google-Attributes: gid107fbf,public
X-Google-ArrivalTime: 1995-02-17 11:06:28 PST
Path: arc1-ca.pugleaf.net!nntp.gmd.de!newsserver.jvnc.net!news.cac.psu.edu!news.pop.psu.edu!ra.nrl.navy.mil!cs.umd.edu!zombie.ncsc.mil!news.mathworks.com!udel!gatech!gt-news!news
From: john.leonard@ce.gatech.edu (John Leonard)
Newsgroups: aus.computers.os2,comp.os.os2.setup
Subject: Re: WinOS2 and the MACH64
Date: 17 Feb 1995 11:45:48 GMT
Organization: Georgia Tech
Lines: 96
Message-ID: <3i229c$iqn@mordred.gatech.edu>
References: <3hcbc5$cn4@sunb.ocs.mq.edu.au> <3hkajr$c9h@charm.magnus.acs.ohio-s <3hpq5j$84@charm.magnus.acs.ohio-state.edu> <3i0kud$qg1@nic.umass.edu>
Reply-To: john.leonard@ce.gatech.edu (John Leonard)
NNTP-Posting-Host: civilstat79.ce.gatech.edu
X-Newsreader: IBM NewsReader/2 v1.02