Re: Xy'd NB

["Patricia M. Godfrey" priscamg@xxxxxxxx]

Michael Norman wrote:
> At 06:44 AM 4/3/2008, Paul Breeze wrote:
> > If I launch NB, switch to full screen, quit, then relaunch (it does
> > relaunch) and try to switch back to normal display I get the following
> > error message:
> >
> > Program error:91
> > NewDisplayMode
> > Object variable or With block variable not set
> When I mimic your sequence, I get the same thing. And the error appeared
> in another sequence of key strokes involving the views.
As I don't have NB, this may be way off base, but from
observation of other older apps (DOS and earlier Win), I can say
that some of them don't do a good job of garbage collection, so
the order in which you run them can be significant. And we all
know that Xy's WYSIWYG is very hard on modern screens. (Recall
the exchange Robert and I had a few years back about an ancient,
underpowered system of mine that could run it full screen, which
no other box could do.) So maybe NB's is too?
As for order of running. last week I went to run dBase 5 for DOS
on the Vista laptop. I'd run it before with no problems (once I
got the screen colors set to something visible, and that's an
issue under all the NT-based Windows versions). Went to enter a
date field, got to the 4-digit year, and the system started
beeping like mad and totally locked up. I had to hit the power
button, then reboot in safe mode.
The--to my mind significant--point was that just before I tried
to run dBase, I had been running my abandonware accounting
package, a Win95 app that just barely runs under Vista (the help
files are inaccessible and I haven't been able to ASSOCiate its
data files with the app). Today, when I went to run dBase right
after booting, it ran fine. So I suspect the accounting package
had left garbage somewhere in RAM that even (hah!) Vista couldn't
 cope with.

--
Patricia M. Godfrey
priscamg@xxxxxxxx