🚀 go-pugleaf

In article <92220.124054IO20456@MAINE.MAINE.EDU> IO20456@MAINE.MAINE.EDU (Ryan Robbins) writes:
>I'm new to using QuickBasic and the BASIC programming language in
>general, and I have run into a problem that even a computer science
>major I work with cannot figure out.
>
>I'm currently in the process of writing a baseball statistics data-
>base. My program has several subroutines. Yesterday when I tried to
>run my program from inside QuickBasic (v4.5), the mouse cursor dis-
>appeared and QuickBasic froze on me. In the lower left hand corner
>of the screen was the word "Binding..." I tried CTRL-BREAK to abort
>the running of my program, but that didn't work. The computer was
>locked, and I had to reboot. I tried running different copies of
>my program (the program I was testing), but none of them worked
>either. So then I tried running QuickBasic and my program on another
>machine - still no luck. Every time "Binding..." appeared on the
>screen's lower left hand corner and the computer locked. What I
>find frustrating is the fact that my program ran perfect and fine
>before. I made no modifications to it before QuickBasic refused to
>run it. Does anybody have an ideas or suggestions to remedy this
>problem?
>

By far the most common cause of this particular problem is saving
you code out to a fast load and save format file after heavy editing.
This can sometimes cause slight corruption in the threaded p-code which
is saved.  You can cure this by loading the program, going to the 
"Save As" menu item of the file menu, and making sure that "Save file
as text (readable by other programs)" option is selected.  

By the way, I highly recommend *never* saving in fast load/save format
for the simple reason that if even one bit is changed from what it should
be (from whatever cause), the entire file is a complete loss.  However, 
You stand a very good chance of recovering most, if not all, of a file
if it is saved in Text format.

Phil Cooper

+>run it. Does anybody have an ideas or suggestions to remedy this
+>problem?
+>
+
+By far the most common cause of this particular problem is saving
+you code out to a fast load and save format file after heavy editing.
+This can sometimes cause slight corruption in the threaded p-code which
+is saved.  You can cure this by loading the program, going to the
+"Save As" menu item of the file menu, and making sure that "Save file
+as text (readable by other programs)" option is selected.
+
+By the way, I highly recommend *never* saving in fast load/save format
+for the simple reason that if even one bit is changed from what it should
+be (from whatever cause), the entire file is a complete loss.  However,
+You stand a very good chance of recovering most, if not all, of a file
+if it is saved in Text format.

Does this continue to hold true for those who conscientiously save as we edit 
so there is a minimal change with each save?

Keith.
-- 
D.K.Higgs  DATA+@osu.edu  a.k.a  dhiggs@magnus.acs.ohio-state.edu _____   __o
Ohio State University Libraries, Acquisitions Department      -------    -\<,
Continuation Acquisition Division                              ------ ( )/ ( )
~~(614)292-6314~~~~~~fax(614)292-2015~~~~~~~~~~\_________/~~~~~~~~~~~~~~~~~~~