Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!ucsd!rutgers!rochester!pt.cs.cmu.edu!dsl.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: LMI Forth(s)
Message-ID: <1739.UUL1.3#5129@willett.pgh.pa.us>
Date: 15 Sep 90 01:22:27 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 31


 Date: 09-12-90 (15:24)              Number: 768 (Echo)
   To: RAY DUNCAN                    Refer#: NONE
 From: KEN BOWERS                      Read: 09-12-90 (22:45)
 Subj: COMMENT                       Status: PUBLIC MESSAGE

 RE:VM386  THE PROBLEM IS THAT THE APPLICATION WILL ONLY START IF THE
 FORTH PROGRAM IS IN FOREGROUND. WHEN THE SYSTEM IS BOOTED AND THE FORTH
 PROGRAM IS IN THE BACKGROUND, IT WILL NOT START, BUT HANGS WAITING. AS
 SOON AS THE VIRTUAL MACHINE IS BROUGHT TO THE FOREGROUND, THE
 APPLICATION BEGINS AND CONTINUES NORMALLY IN BACKGROUND. THE FORTH
 PROGRAM DOES NOT FORCE A SWITCH, BUT MUST BE SWITCHED INORDER TO START.

 NET/Mail : LMI Forth Board, Los Angeles, CA (213) 306-3530             

 Date: 09-12-90 (22:45)              Number: 769 (Echo)
   To: KEN BOWERS                    Refer#: 1664
 From: RAY DUNCAN                      Read: NO
 Subj: COMMENT                       Status: PUBLIC MESSAGE

 Sounds like the video mode switch to 80x25 text mode that Forth requests
 when it starts up is causing your problem then.  I suppose VM386
 requires the mode switching session to be in the foreground to simplify
 the task of virtualizing the display.  You can revector the IDENT word
 so it doesn't call VINIT (see the "internals" section of the manual
 which lists the vector locations).

 NET/Mail : LMI Forth Board, Los Angeles, CA (213) 306-3530             
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: uunet!willett!dwp or dwp@willett.pgh.pa.us