Text 1403, 47 rader
Skriven 2009-12-31 13:38:20 av Mike Luther (1:117/3001.0)
Ärende: Curing WordStar 7 SYS errors
====================================
Of all things, I stumbled on how to cure the WordStar Version 7 for DOS SYS3170
errors in OS/2 DOS-VDM sessions!  I've been looking for this solution for YEARS
now....

The problem exists when you open up a DOS-VDM session in OS/2 and fire up
WordStar 7 from any shell or .BAT file; whatever.  If you type in the file name
you wish to edit and hit the <CR> to open it real quick, real often you will
see WS7 cause a SYS3170 error.  After that happens you will see that the
WordStar FILENAME.WST temporary files such as FILENAME.$A$ and FILENAME.$B$ are
still there after this error.  You will have to delete them before you can open
that file for edit again.

What I'd sort of learned to do was to type the file name in, then count to
three - 1, 2, 3 - then punch the <CR> key to open it which prevented this deal.

I've asked and asked about this deal to no avail!

OK .. here is how I fixed it!

  In the #:\WS program directory use the WSCHANGE setup program.

      WSCHANGE - (for your default program name)
      Enter "D" for WordStar files
      Enter "B" for Editing settings
      Enter "B" for Typing settings
      Enter "E" for DISK ACCESS PAUSE or DDISK settings.

      I've seen this as either the number 3 or 5 in many boxes now.

      Change the numer to the number 10 (Ten) and save the changes.

Poof!  The whole WS7 operations has been running PERFECTLY for file load
operations on a whole bunch of boxes on everything from Warp FP17 last to
Merlin MCP2 latest XRC5 Fix Pack versions.  No more SYS errors on file opening
stuff!  Your selected file opens in a split second just perfectly every time as
far as I can see now.

Probably won't help anyone else here but if it does that's why I'm posting
this!


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)