
 
INFO-ATARI16 Digest         Wed,  7 Mar 90       Volume 90 : Issue  291
 
Today's Topics:
                  DMA Programming... DLII-Boot Read
                        Gemini and Gulam Woes.
           How do you create non-scrolling screen regions?
                               METAFONT
                             Question..??
                        Quick ST 2.0 (2 msgs)
                       RWABS TRAPPING ERRORS...
          Subject: Sooner or later it _will_ happen to you.
----------------------------------------------------------------------
 
Date: 1 Mar 90 13:55:04 GMT
From:
 cica!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!mips!prls!philabs!ttidca!wo
 odside@tut.cis.ohio-state.edu  (George Woodside)
Subject: DMA Programming... DLII-Boot Read
Message-ID: <10382@ttidca.TTI.COM>
 
In article <1990Feb28.122940.2051@ux1.cso.uiuc.edu> cs325ec@ux1.cso.uiuc.edu
 (Gregory Lemperle-Kerr) writes:
...[edited]...
>       Does anyone know how DLII accomplishes the reading of boot sector
>       0 of a hard drive?  Must this be done in assembler, or can I do
>       it with Turbo C?
 
You can do it with whatever you please. It is nothing more than a Rwabs
function call.
 
Rwabs normally accesses the drive as a logical device, so a read of
sector 0 will return logical sector 0 of a drive. If you set the
absolute address bit (bit 4, I believe), it will read the physical
sector 0 (partition map) of a partitioned drive. If the drive is not
partitioned, physical and logical sectors are the same.
 
> Also: if I change the partition info on the boot sector and reboot,
>will everything conform?
 
Conform to what? A trashed drive? Yes. A drive with a different partitioning
scheme? No. Partitioning a drive is vastly more complex than just the
values in the partition maps and boot sectors. If you don't know what
you are doing, I strongly recommend good backups prior to experimentation.
 
>Also:  I noticed that ICD allows more than 4 partitions/drive
>       by turning to $156 offset after filling those starting
>       at $1c6... is this OK and compatible with everything?
 
No. It is specific to the driver you are using. The original Atari
partitioning system supported four partitions. The extended method
devised by SUPRA is what you are describing, and is supported by
SUPRA and ICD (I think Astra also used it). The extended partitioning
announced by Atari with HDX 3 is not the same.
--
* George R. Woodside - Citicorp/TTI - Santa Monica, CA *
* Path:       woodside@ttidca                          *
*   or:       ..!
 
------------------------------
 
Date: Tue,  6 Mar 90 13:31:10 EST
From: SKOLODZIESKI@VAXB.STEVENS-TECH.EDU (aluminum foil ball)
Subject: Gemini and Gulam Woes.
Message-ID: <9026133111.24401c79.SKOLODZIESKI>
 
 
        I love GEMINI, it is all one could ask for in a desktop. The only
problem I have is when running Gulam from Gemini. It I call gulam, "Gulam.tos"
it will run fine in the slow <console> window. But if I call  gulam "Gulam.prg"
it will clear the screen and run just as iff it was clicked from the desktop.
The hitch is, after exiting gulam and getting back to the GEMINI desktop, I
cannot renter gulam. It just clears the screen, then pops back to the GEMINI
destop. This is killing me. Any thoughts on this????
 
 
   Scott Kolodzieski
   Stevens Institute of Technology
   skolodzieski@vaxc.stevens-tech.edu
------------
 
------------------------------
 
Date: 6 Mar 90 22:07:13 GMT
From:
 mips!zaphod.mps.ohio-state.edu!sunybcs!uhura.cc.rochester.edu!rochester!rit!ult
 b!ajy2208@apple.com  (A.J. Yarusso)
Subject: How do you create non-scrolling screen regions?
Message-ID: <2344@ultb.isc.rit.edu>
 
Hi everyone,
 
  I need to know how to create region(s) on the screen that are
independent from normal screen i/o (mainly, scrolling..).  Most terminal
programs have a line or two somewhere on the screen that doesn't scroll.
Usually these are status displays to show useful information (baud rate,
system connected to, various toggles, etc..).
 
  I've searched my wonderful MWC manual, but there's no mention on how
to create something to this effect.  If I had $250 to plunk down for
developer docs, I'd do that.  If Atari was more leniant with disclosure
of USEFUL information for the ST, I might be able to buy books that
describe just what I want to do.  In that respect, the 8-bit was much
more enjoyable to program than the ST.  Hmm, it seems that my request
for help is becoming a flame, so I'll cool my jets now..
 
  Hopefully I won't have to write custom screen i/o routines to do
this..  Ahh, I wish the ST had a display list..  :-)
 
_____________________________________________________________________________
 Albert Yarusso, Rochester     ajy2208@ritvax.bitnet
 Institute of Tech. _________________________________________________________
 Computer Science  /___   /    
______________________/  /     ajy2208@ultb.cs.rit.edu     GEnie:  A.Yarusso
 
------------------------------
 
Date: Wed, 07 Mar 90 13:48:00 GMT
From: Mr. Stephen Culshaw
 <XUUM24%PRIME-A.CENTRAL-SERVICES.UMIST.AC.UK@Forsythe.Stanford.EDU>
Subject: METAFONT
Message-ID: <$TGJHCZFZCRGR at UMPA>
 
I have been using METAFONT to generate various fonts for the Atari
TeX previewer SHOWDVI.TTP. I have hit a problem and with only very limited
knowledge of METAFONT, I would appreciate any suggestions as to the cause
of the fault. I have been able to generate the 144gf and 249gf sizes but
when I try to generate the 173gf, this is what I get.
 
This is METAFONT, C Version 1.5 (no base preloaded)
** \mode=catari;\mag=1.802;input cmss10
(.\cmss10.mf (.\cmbase.mf) (.\roman.mf (.\romanu.mf [65] [66] [67] [68]
[69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81] [82] [83]
[84] [85] [86] [87] [88] [89] [90]) (.\romanl.mf [97] [98] [99] [100] [101]
[102] [103] [104] [105] [106] [107] [108] [109] [110] [111] [112] [113]
[114] [115] [116] [117] [118] [119] [120] [121] [122]) (.\greeku.mf [0]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]) (.\romand.mf [48] [49] [50] [51]
[52] [53] [54] [55] [56] [57]) (.\romanp.mf [36] [38] [63] [62]) (.\romspl.mf
[16] [17] [25]
! bad pos.
<to be read again>
                   ;
pos->...XPR3)<=currentbreadth:errmessage"bad pos";
                                                  fi.fi(x(SUFFIX2)r-x(SUFFIX...
l.84 pickup tiny.nib; pos11(right_curve,0)
                                          ;
? [26]
! bad pos.
<to be read again>
                   ;
pos->...XPR3)<=currentbreadth:errmessage"bad pos";
                                                  fi.fi(x(SUFFIX2)r-x(SUFFIX...
l.138 pickup tiny.nib; pos11(right_curve,0)
                                           ;
?
 
 
Also does any one have the neccessary .MF file for generating the fonts
for the Atari SLM804. Someone posted me a .MF file previously but it
required a couple of files that I've not been able to find - ie. PLAIN.MF
version 1.0a and the corresponding CMBASE.MF - does anyone have them.
The problem relates (I think) to the Atari laser being 'write-white'
 
 
% stlaser mode: to generate fonts for the Atari ST laser printer SLM804
mode_def stlaser =
 proofing:=0;                  % no, we're not making proofs
 fontmaking:=1;                % yes, we are making a font
 tracingtitles:=0;             % no, don't show titles at all
 pixels_per_inch:=300;         % that's pretty low resolution
 blacker:=-.25;                % less blackness
 fillin:=.5;                   % compensate for diagonal fillin
 o_correction:=0;              % normal overshoot
 write_white_engine:=true;     % You have to use the modified PLAIN.MF V1.0a
                               % and the corresponding CMBASE.MF, which has
                               % to be modified according to TUGboat 1/1987)
 enddef;
 
 
Thanks for any help
 
Steve C.
xuum24
 
 
 
------------------------------
 
Date: 6 Mar 90 22:06:25 GMT
From: tiamat!mjbtn!raider!dlh@uunet.uu.net  (Dana L. Holt)
Subject: Question..??
Message-ID: <188@raider.MFEE.TN.US>
 
        <This is a re-post due to the fact that I only got 1 reply>
 
        Ok, I have a program I have written in assembly. It replaces the
Alt-Help (print screen) vector. It pops when Alt-Help is pressed. Well,
when I press Alt-Help I get my menu. I can select from the menu, but
when I try to do any disk access it locks the machine. If I press 'X' for
exit on the menu it returns to the Desktop or current program just fine.
It doesn't mess up until I try to do disk access, can ANYONE help me out?
Do I need to disable an interrupt or something? Thanks in advance!
                        dlh@raider.MFEE.TN.US
P.S. E-mail OR post on the net, doesn't matter.
 
------------------------------
 
Date: 7 Mar 90 06:58:15 GMT
From:
 zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!xanth!xanth.cs.odu.edu!scott@
 tut.cis.ohio-state.edu  (Scott Yelich)
Subject: Quick ST 2.0
Message-ID: <SCOTT.90Mar7015815@offa.cs.odu.edu>
 
> I read the press release on the new Quick ST 2.0 and it mentioned something
> about a demo.  I was wondering if anyone knows where I could get this on the
> net or if anyone could send it to me.  I would like to see how this beast
> works.  Thank you.
 
Speaking of Quick ST.... has anyone had any experience with Gemini?  It looks
pretty decent... but when I try to couple Gemini's console window with
gulam and I have quick BIOS text set from Quick ST, I get some trash on the
screen.
 
And now for a random thoughts:
1) Information on that disk to disk copy scheme as well as the space ace
   demo are available through ftp from xanth.cs.odu.edu.
2) Could someone kindly tell me the latest versions of the following programs?
   unix windows, quick st, picswitch, ka9q (slip), uniterm, minix (st)
3) Does anyone have problems with Publishign Partner crashing a lot?
   And, is it correct that I read that the font creator would allow you
   create fonts that would only work on a non-Postscript printer?
I know I haven't given my setup, but things change so quickly, who
knows what it will be by the time you read this.
 
------------------------------
 
Date: 6 Mar 90 21:42:05 GMT
From: agate!darkstar!ucscb.UCSC.EDU!rome@ucbvax.Berkeley.EDU
Subject: Quick ST 2.0
Message-ID: <1664@darkstar.ucsc.edu>
 
I read the press release on the new Quick ST 2.0 and it mentioned something
about a demo.  I was wondering if anyone knows where I could get this on the
net or if anyone could send it to me.  I would like to see how this beast
works.  Thank you.
 
       Roman Baker
       rome@ucscb.UCSC.EDU
 
------------------------------
 
Date: 5 Mar 90 18:25:52 GMT
From: att!dptg!lzsc!hcj@ucbvax.Berkeley.EDU  (HC Johnson)
Subject: RWABS TRAPPING ERRORS...
Message-ID: <1358@lzsc.ATT.COM>
 
In article <16000019@ux1.cso.uiuc.edu>, cs325ec@ux1.cso.uiuc.edu writes:
>
>
>       Yet another Rwabs question:
>
>       Can anyone tell me how to trap the call to the dialog
>       box which says something to the effect of Data in
>       Drive X: is damages... ?
>
The reason the call is there is that you are DEAD if the disk fails.
 
I suspect that you are trying to scan the disk for bad sectors, and don't
want the message.  If so, try OR-ing 0x8 to the command word.  Supra
and or ICD use this to turn off retries, and I would suspect it will also
stop the dialog box  call as well.
 
 
Howard C. Johnson
ATT Bell Labs
att!lzsc!hcj
hcj@lzsc.att.com
 
------------------------------
 
Date: Mon, 5 Mar 90 14:23+0100
From: Ritzert%DMZRZU71.BITNET@Forsythe.Stanford.EDU
Subject: Subject: Sooner or later it _will_ happen to you.
Message-ID: <900305132338.807867@DMZRZU71-UNI-MAINZ--GERMANY>
 
<Over the weekend I managed to completely blow away my hard drive.  It wouldn't
<boot, it wouldn't talk to my ST at all, even when I ran AHDI from floppy.
<
<Wouldn't do _nuthin'_.
<
<c60 meg, gone, all gone.
<
<Would you beleive that this has a happy ending?  I had just made
 
Well, it looks like the drive "felt formatted". This happens sometimes;
I know several people who have had these problems. It also happened to
me with the sh205 a few weeks ago. After I had reformatted the drive (of
course!), someone who has faced this problem several times told me of a
way to restore the drive, at least the partitions above c:\. He told me
that usually only the first 8-10 kB were zeroed. So it was possible to
reconstruct the later partitions with a hd-sector-editor like Supra's
supedit.prg. Of course You have to know about the physical structure on
the disk. So it is recommendable to use such a tool to extract the
formatting and partitioning information, write it onto a sheet of paper
and attach that to the case of You drive.
 
Does anyone (eventually Atari engineers?) know about the reason for this
problem? Even the people mentioned above --- all very experienced, doing
hardware development for the ST and other computers --- had no idea.
 
Michael Ritzert
mjr@dmzrzu71.bitnet
 
------------------------------
 
End of INFO-ATARI16 Digest V90 Issue #291
*****************************************