From: Tim Schreiner
Subject: Re: PowerBasic 3.5 BUG!!!
Suggestion for a work-around:
I use a different (multi-file) editor for writing code, and use the IDE
for catching syntax errors and debugging sessions.
Tim Schreiner
Dave Navarro wrote:
>
> In article , zarmand@concentric.net says...
> > Terry Brown wrote:
> > >
> > > Hi all,
> > > here's a MEGA problem I discovered with the PowerBasic editor.
> > > 1) Take a file you're not worried about getting corrupted, and view it
in
> > > the editor.
> > > The file should be about 450 lines long, and roughly 45 char. per
line.
> > > 2) Open another file, and copy a line from it in to the clipboard.
> > > 3) Paste it to the first file.
> > > 4) OK, so everthing seemed to go OK right?
> > > WRONG!! take a look at the last 20 or 30 lines of your program
ode.
> > > If your lucky, it's just got corrupted. If your unlucky like I was,
half
> > > the lines
> > > are missing, and the rest are garbage.
> > >
> > > This is using 3.5 with the upgrade....
> > > Anyone else had the same problem?
> > >
> > > It doesn't seem to happen if you don't use the clipboard.
> > > bfn
> > > T..
> >
> > I had that happen at least once and never figured out what happened. Now
> > I will give it a try. It seems to me it happened during a cut/paste
> > thing also, but I never figured out exactly what happend because PB3.5
> > jumps around so much anyway when you delete a line or something. I'll
> > give it some more testing and see. If it is a bug, then it will not be
> > the first one.
> >
> > If it makes a difference, I run WIN95 and use a DOS window for PB3.5. I
> > set max memory available and make the mouse exclusive in a full screen
> > window. It seems to work fine for me so far...but I am a tyro as far as
> > PB3.5 goes....used PDS7.1 for years and years....
>
> I just wanted to let everyone know that we are aware of this problem.
> Unfortunately, it is very difficult to reproduce. Whether or not the bug
> manifests itself or not is highly dependant on you memory configuration.
he
> details of which our developers are still working on.
>
> What I do know is that if this problem does happen on your system, any kind
of
> change to your memory management (or memory manager) will likely cause the
> problem to go away. However, before you do that, I would appreciate it if
you
> would use the DOS MEM.EXE utility to do a memory dump and email the results
to
> me or our support department (support@powerbasic.com).
>
> --Dave
*** QwkNews (tm) v2.1
* [TN71] Internet Newsgroup: alt.lang.powerbasic
--- GEcho 1.20/Pro
---------------
* Origin: Toast House Remote (1:100/561)
|