Xref: utzoo comp.sys.att:6615 comp.lang.smalltalk:1120
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!uunet!peregrine!ccicpg!zardoz!tgate!irsx01!ka3ovk!drilex!axiom!linus!mbunix!bwk
From: bwk@mbunix.mitre.org (Barry W. Kort)
Newsgroups: comp.sys.att,comp.lang.smalltalk
Subject: Re: AT&T 6300+ ROM BIOS problem
Summary: Good suggestions from Dean, but I've tried them already.
Keywords: DigiTalk SmallTalk V/286
Message-ID: <54810@linus.UUCP>
Date: 31 May 89 18:56:04 GMT
References: <54627@linus.UUCP> <3134@sun.soe.clarkson.edu>
Sender: news@linus.UUCP
Reply-To: bwk@mbunix (Barry Kort)
Organization: Moribund Corporation, Seventh Chapter, DE
Lines: 41

In article <3134@sun.soe.clarkson.edu> dean@sun.soe.clarkson.edu
(Dean Swan) responds to my earlier plea for help on DigiTalk
SmallTalk V/286, which does not run on my AT&T PC 6300 Plus:

 > - First, It sounds like you're using a something less than legitimate
 >   copy.  If I'm wrong, ignore this comment.  If not, have the boss buy
 >   you another copy.

By now we have bought some half-dozen copies.  I assure you DigiTalk
isn't losing money on us.

 > - Smalltalk V/286 can switch between protected and real modes in a
 >   couple of different ways.  The master disks come with a program
 >   to help you determine the way that works best on your machine. 
 >   If the default method doesn't work which sounds like your problem,
 >   then you have to specify a command line switch to use the alternate
 >   method.

Yes, I tried all 4 combinations of the /S (shutdown) and /T (restart)
switches.  Machs nix.

 > - Also, depending on what else you use your extened memory for, you
 >   may have to set some other command line switches to tell Smalltalk
 >   to stay out of certain areas of extended memory.  This is explained
 >   in an appendix of the manual.

I tried the /X, /D/ and /U command line options to keep V/286 from
trying to access the extra 384K on the motherboard, which, for reasons
unbeknownst to me, are assigned noncontiguously to the high-address
end of the machine's memory address limit.  I'm now considering a
suggestion to rip out the extra 384K to see if that is what's tripping
up V/286.

 > Hope this helps some!

I don't wish to sound unappreciative.  I do thank you for your advice.
I'm still looking for an existence proof that V/286 can be made to
run on the 6300 Plus, before I continue with more exploratory
neurosurgery on the motherboard.

--Barry Kort