ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) (05/08/91)
Date: 05-02-91 (17:49) Number: 2081 of 2088 To: GARY SMITH Refer#: NONE From: BEN COMBEE Read: NO Subj: NEPHYTE NEEDS F83 EXAMPLE Status: PUBLIC MESSAGE Conf: FORTH (58) Read Type: GENERAL (+) ZDBDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBD? 3o3 QUOTED FROM <GS> 3o3[ 3o3 3o3[ 3o3 I recently download Laxen and Perry F83 from my local BBS and 3o3[ 3o3 started using it however I am have a small problem ... I can 3o3[ 3o3 only access files while I am on drive A. Does anybody know a 3o3[ 3o3 work-around for this? 3o3[ @DADDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDADY[ ______________________________________________________________________ You need to re-metacompile it on the drive it's on. This will set the file paths right in the program. -( Ben )- --- ~ SLMR 1.05 ~ I just got pulled over by the LAPD, and boy, am I beat! ~ RNet 1.08D:* Metrolink - Front Porch BBS 404-695-1889-DS-Super Regional HUB PCRelay:DCINFO -> #16 MetroLink (tm) International Network 4.10 DC Info Exchange MetroLink International Hub <<<>>> ----- This message came from GEnie via willett. You *cannot* reply to the author using e-mail. Please post a follow-up article, or use any instructions the author may have included (USMail addresses, telephone #, etc.). Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp
ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) (05/28/91)
Category 1, Topic 33 Message 35 Sat May 25, 1991 P.VARN [Paul Varn] (Forwarded) I couldn't find another place to post a request for help. I'm trying to learn Forth on the Atari ST. I have the '83 version of Brodie's book but I'm having trouble with starting out. I can't figure out how to create a new file so I can open and edit it. I also can't figure out how to remove or add blocks to a file. The implementations I've tried are: F83.TOS and F65K.TOS. Can anyone suggest a better documented ST Forth to learn from or give me some hints on the ones I've tried to get me over the starting learning curve? Thank you. -Pv- ----- This message came from GEnie via willett. You *cannot* reply to the author using e-mail. Please post a follow-up article, or use any instructions the author may have included (USMail addresses, telephone #, etc.). Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp
ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) (05/28/91)
Category 1, Topic 33 Message 36 Sat May 25, 1991 P.VARN [Paul Varn] (Forwarded) I made a small error in my lat post. Should have been F68K.TOS NOT F65K.TOS. -Pv- ----- This message came from GEnie via willett. You *cannot* reply to the author using e-mail. Please post a follow-up article, or use any instructions the author may have included (USMail addresses, telephone #, etc.). Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp
ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) (05/28/91)
Category 1, Topic 33 Message 38 Sat May 25, 1991 P.VARN [Paul Varn] (Forwarded) Thanks ELLIOT.C for your note. When you mentioned TOP and IND, TOP is some kind of screen position? I couldn't find any reference to IND or do you mean INDEX? Your mention of CREATE-FILE is interesting. That's the command I've been tryin to use that locks up when I use it. Every mention I've seen of it has cloudy reference to its use syntax. You've given me a good clue with n CREATE-FILE <name>. I'm going to give that a try. Any other handy file specific words I should know? At one point I did manage to save and open a file I created by re-naming an existing file from the OS and using the Forth editor to WIPE the blocks. I then wrote into them, saved and opened them. One of my blocks where I tried a wild experiment loaded and executed (something REALLY simple). I tried the teaching example from the beginning of Brodie's book in another block and it wouldn't load and execute although there was nothing wrong with the text. I'm off to do some more playing. If someone has a suggestion for any text in the library that might address some beginner questions and words specific to the ST I have an ear. -Pv- ----- This message came from GEnie via willett. You *cannot* reply to the author using e-mail. Please post a follow-up article, or use any instructions the author may have included (USMail addresses, telephone #, etc.). Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp
ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) (06/04/91)
Category 1, Topic 33
Message 40 Sun Jun 02, 1991
F.SERGEANT [Frank] at 23:07 CDT
Maybe I shouldn't butt in regarding your Atari & F83 questions, Paul,
but I will anyway. I don't have an Atari so I'll assume you have a version
of F83 that is almost identical to the IBM PC version and make my suggestions
accordingly.
What you should do to start with is _read_ the documentation that comes
with F83. It should tell you how to approach becoming familiar with F83.
Most of its documentation is not in the form of text files, manuals, etc., so
it should be a simple matter to read what _is_ in such form. Then follow its
suggestions regarding VIEWing words. Use VIEW on a likely prospect (such as
OPEN or CREATE-FILE) to get you into the general area of the source code.
Then read the source code and the shadow screens that go with it. Don't just
read the one screen that VIEW throws you into: also read the surrounding
screens (using N and B or whatever the editor commands are that move forward
one screen or back one screen; A should switch between source and shadow
screens). Make note of other words used within the definitions of the word
you are VIEWing so you can VIEW those words also. A way to get likely
candidates to VIEW is to type WORDS and see the words in the vocabulary.
Beware that some of the words you need to research may reside in a different
vocabulary (such as DOS or HIDDEN or ???) so you may need to change
vocabularies and do WORDS several times. Eventually you will be able to find
the exact word to create a new file, _and_ its stack comment (so you'll know
how to use the word). This is one of the beauties of a system that comes
with complete source code.
Your method of copying an existing file to a new name and erasing all
its text and then using the file for your own purpose is also a perfectly
workable method for making a new file.
Now, _why_ didn't that Starting Forth example you typed in work? Again,
you should research it. To do this you should study the example to
understand what it is doing and how it goes about it. Then try typing in the
example word by word (you can't type in the looping, branching, >R R@ R> type
words), checking the stack after each one, perhaps DUMPing memory or checking
the values of VARIABLEs, in order to actually see what is happening. (By
typing in the example, I mean to execute the parts of each definition, one by
one, from the keyboard.) Another possibility is to use F83's trace or debug
facility, but I might recommend you delay that until you've tried the method
I just suggested. By using this system you will locate an F83 word that
doesn't do what you expected it to from the Starting Forth example. Then use
VIEW and study its source and shadow code until you understand the difference
and can adjust for it.
If you follow these suggestions, please post a follow up letting us know
how it all works out.
-- Frank
-----
This message came from GEnie via willett. You *cannot* reply to the author
using e-mail. Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp