CompuServe Messages

#I got 2.0 ROMS! Yeah!

    05-Nov-91 22:35:36
Fm: Steven D. Kapplin 70055,1021
To: Andy Finkel 70007,4173
Andy, I just picked up a book at B. Daltons on 2.0 and there was your name above a quote. I didn't realize you are CBM's 2.0 Man! Your just the expert I should talk with, huh? OK, I understand what you're telling me. Since I'm mapping ROM into fast memory, then I guess I have to use SetCPU. However, I noted that when I turned the data cache and fastrom off with SetCPU, then ran Enforcer quiet (before binddrivers) the BB didn't work. I'll change my startup and try using Enforcer only and leave burst mode off and fastrom off and see how the BB performs. On some other matters, I noted that the docs don't provide any info on Fountain, although not much is needed to figure it out, some users won't even realize its existence. I used Fountain to get all my Adobe fonts into the Fonts: directory and create the .font and .otag files. I then tried a PD program, NewAF, which is a commodity that forces AvailFonts() to cache the scalable fonts so my WP programs would access them. Is there some other way to accomplish this? Nothing in the docs deals with the use of the scalable fonts other than that they can be used for onscreen usage. Do I need to create normal font files for them to get the screen bitmap fonts, or isn't that necessary with the scalable fonts? I also learned that you cannot snapshot window sizes and positions when you use the View Name mode of file display. Snapshotting only seems to work when View Icon mode is used. I guess this is a "missing feature", but I'd like to suggest that it should be possible to shapshot regardless of view mode. I spent almost two hours trying to figure out why I couldn't get the snapshots to "take". I'd also like to note that the ARexx docs are OLD. They are version 1.0 docs and don't document the new functions added thru version 1.15. Not that I'm complaining, Andy! Release 2.0 is truly a marvel relative to 1.3 and I agree with the quote of you saying that "once you try 2.0 you'll never want to go back to 1.3." It's a major step forward, but the documentation could go further.