Thread View: net.micro.atari
5 messages
5 total messages
Started by Vicious Oyster
Mon, 17 Feb 1986 19:58
1040ST and ROM TOS questions
Author: Vicious Oyster
Date: Mon, 17 Feb 1986 19:58
Date: Mon, 17 Feb 1986 19:58
16 lines
1331 bytes
1331 bytes
*** ***
Since we now have an official source for Atari news here on USENET,
could we get beyond the rumors of what the 1040ST actually is?
What I've gathered is that it will be 100% compatible with 520 software,
have 1 meg of RAM, TOS on ROM, a double sided drive, a list price of
$200 more than the 520, and come nicely packaged in a single box. Is
that correct? Any additions?
About TOS in ROM... a friend has a 520ST, and would like to know how
one goes about getting the ROM chips. Should they be available from
dealers, or do you have to go directly to Atari?
- Joel ({allegra,ihnp4,seismo}!uwvax!uwmacc!oyster)
P.S. Jim at Nicolet-- you've got a customer for your first 1040ST. I'd be
interested in hearing what you know about availability.
Loading and sizing fonts...
Author: Steve Tynor
Date: Tue, 18 Feb 1986 01:11
Date: Tue, 18 Feb 1986 01:11
19 lines
1469 bytes
1469 bytes
The last time I asked Richard Frick when a Font Editor/Loader would be
available for the ST, he said 'maybe never.' Has this changed? Does the
VDI load_font routine work, or is yet another of the VDI functions that DRI
hasn't gotten around to implementing?
Also, I've been trying to figure out how to scale down the system font to a
smaller size. I've been able to use vst_height() call to increase the
character size, but every time i try to shrink it I get mushrooms. How does
one get the small font that Icons are labeled with and the Doodle prog uses?
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
No problem is so formidable that you can't just walk away from it.
Steve Tynor
Georgia Instutute of Technology
...{akgua, allegra, amd, harpo, hplabs,
ihnp4, masscomp, ut-ngp, rlgvax, sb1,
uf-cgrl, unmvax, ut-sally} !gatech!gitpyr!tynor
Re: 1040ST and ROM TOS questions
Author: neil
Date: Tue, 18 Feb 1986 19:50
Date: Tue, 18 Feb 1986 19:50
21 lines
1623 bytes
1623 bytes
***** In article <1973@uwmacc.UUCP>, oyster@uwmacc.UUCP (Vicious Oyster) writes: > Since we now have an official source for Atari news here on USENET, > could we get beyond the rumors of what the 1040ST actually is? > What I've gathered is that it will be 100% compatible with 520 software, > have 1 meg of RAM, TOS on ROM, a double sided drive, a list price of > $200 more than the 520, and come nicely packaged in a single box. Is > that correct? Any additions? > About TOS in ROM... a friend has a 520ST, and would like to know how > one goes about getting the ROM chips. Should they be available from > dealers, or do you have to go directly to Atari? The 1040ST also has a built-in power supply for both the computer and the drive. It looks like a 520 except for a couple of extra inches in the back of the system Otherwise, exactly as described above. Look for the next issue of Byte (March 1986) to have a full preview of the 1040ST. The ROM chips are available from dealers. Suggested price is $25. If your dealer does not know about them, tell the dealer to call Atari's service dept.
Re: Loading and sizing fonts...
Author: Bruce Holloway
Date: Wed, 19 Feb 1986 17:52
Date: Wed, 19 Feb 1986 17:52
37 lines
2255 bytes
2255 bytes
In article <1436@gitpyr.UUCP> tynor@gitpyr.UUCP (Steve Tynor) writes: >Does the >VDI load_font routine work, or is yet another of the VDI functions that DRI >hasn't gotten around to implementing? Digital Research is not responsible for writing Atari's VDIs. If there are any unimplemented functions, talk to Atari. Also, the VDI specification allows for functional subsets. These limitations can usually be found in the return from the Open Workstation call, the Extended Inquire function, and the other Inquire Functions. To answer your question though, Load Fonts is implemented. The reason it is so difficult to create a font is due to the odd format fonts are required to use. But I can't believe that no one will come out with a font editor! Didn't I see one in ANTIC a while back? > >Also, I've been trying to figure out how to scale down the system font to a >smaller size. I've been able to use vst_height() call to increase the >character size, but every time i try to shrink it I get mushrooms. How does >one get the small font that Icons are labeled with and the Doodle prog uses? > The system font can not be scaled down; in fact, no font can be. They can, however, be doubled in size, but that's it. Please send the code that creates the Unhandled Exception (aka mushrooms) so that I can see why it's failing. I'm working on a new set of VDIs now, and I'd really like to know why this happens. -- Bruce Holloway Digital Research, Inc. 60 Garden Court Monterey, CA 93942 ....!ucbvax!hplabs!amdahl!drivax!holloway (I'm not THAT Bruce Holloway, I'm the other one.)
50 Line Screen
Author: Glen Stone
Date: Fri, 21 Feb 1986 18:18
Date: Fri, 21 Feb 1986 18:18
112 lines
8652 bytes
8652 bytes
These routines are taken from Comp-U-Serve. They allow you
to put a mono-system into 50 line mode and back again.
Question: How do they work ??? They index in the negative direction
from the pointers received in the line A call. My line A documentation
says nothing about anything in the negative direction.
Note: the fifty lines are quite nice... for those who are writing terminal
programs, editors, etc. this would be I nice option. I've modified some
of the public domain stuff to include this.
Note1: You can also have a 4x4 font but that hurts.
* Make hi rez screen bios handle 25 lines of 8x16 characters
*
*
* author:
* j d eisenstein
*
* date:
* 15-aug-85
*
.text
.global _hi25
LINEA_INIT equ $A000
GET_REZ equ 4 ; extended bios resolution inquiry
_hi25:
lea stack,sp
move.w #GET_REZ,-(sp) ; get screen resolution
trap #14
addq.w #2,sp
cmp.w #2,d0 ; only execute if already in hi rez
bne exit
dc.w LINEA_INIT ; get the important pointers
move.l 08(a1),a1 ; a1 -> 8x16 font header
move.l 72(a1),-$0A(a0) ; v_off_ad <- 8x16 offset table ad
move.l 76(a1),-$16(a0) ; v_fnt_ad <- 8x16 font data addr
move.w #0016,-$2E(a0) ; v_cel_ht <- 16 8x16 cell heigh
move.w #0024,-$2A(a0) ; v_cel_my <- 24 maximum cell "Y"
move.w #1280,-$28(a0) ; v_cel_wr <- 1280 vertical byte offset
exit: clr.w -(sp) ; back to the os
trap #1
ds.l $10
stack: ds.l $01 ; hey chef, gimme a short stack
end
* Make hi rez screen bios handle 50 lines of 8x8 characters
*
*
* author:
* j d eisenstein
*
* date:
* 15-aug-85
*
.text
.global _hi50
LINEA_INIT equ $A000
GET_REZ equ 4 ; extended bios resolution inquiry
_hi50:
lea stack,sp
move.w #GET_REZ,-(sp) ; get screen resolution
trap #14
addq.w #2,sp
cmp.w #2,d0 ; only execute if already in hi rez
bne exit
dc.w LINEA_INIT ; get the important pointers
move.l 04(a1),a1 ; a1 -> 8x8 font header
move.l 72(a1),-$0A(a0) ; v_off_ad <- 8x8 offset table addr
move.l 76(a1),-$16(a0) ; v_fnt_ad <- 8x8 font data addr
move.w #008,-$2E(a0) ; v_cel_ht <- 8 8x8 cell height
move.w #049,-$2A(a0) ; v_cel_my <- 49 maximum cell "Y
move.w #640,-$28(a0) ; v_cel_wr <- 640 offset to cell Y+
exit:
clr.w -(sp) ; back to the os
trap #1
ds.l $10
stack: ds.l $01 ; stack em up an blow em out
end
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads