Marc,

My experience is the opposite of yours. Win98 and 6.1 locked up randomly and
several times daily on my first two RBase for Windows 6.1 applications and I
was baffled and extremely frustrated after trying everything this great list
suggested (including replacing the NICs, and reformatting and installing
clean installs of Win98).

When I finally replaced the troubled Compaq Presarios w/ Celeron processors
with refurbished Compaq workstations (business class machines with real
Pentium processors at about $ 800.00 each) all problems disappeared.   Any
problems I see now are machine specific (see below).

The same exact RBase for Windows 6.5++ programs (and several newer ones) now
run on XP processing 300 orders a day with 4-5 concurrent users using these
programs with ZERO problems. I have 30 total local users most using only
RBase for Dos apps.  I couldn't be happier with XP and 6.5++.

We did have one XP that started freezing up occasionally after the user
changed from the XP default display theme and colors.  The problem seems to
be gone now that we changed her back to the Windows default theme and
removed some unauthorized programs and screen savers she had downloaded from
the Internet.

The problem computers seemed to run DOS RBase apps just fine.

Good luck with debugging your problem.  Mine drove me crazy for months.

Kenny Camp
IT Manager
Electro Enterprises
Oklahoma City, OK

----- Original Message ----- 
From: "marc schluter" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 06, 2004 10:18 AM
Subject: [RBASE-L] - XP and 6.5++ major problems


> Hi all
>
> I have been using RBase for years and had 0 problems
> using 6.1 in 98.  When I switched to XP and 6.5++
> about a year ago it turned into crash city.  This is
> not too bad until you start haveing broken pointers
> and need to go to your back up.  I am not sure if it
> is a XP problelm, hardware, RBase, my app or a
> combination.
>
> My db is about 100 meg (all 4 files) and over 100,000
> rows in my main transaction table.  I have RStyled all
> files, added more RAM, and have been using the error
> feature (set var v1err = (cval('error detail'))
> ) to track errors.  I have fixed all errors I can
> find.  The problem with this is when you crash to
> Windows you can't get the error.
>
> The program does not crash in the same place and you
> can not duplicate the problem.
>
> I am starting to upgrade to 7 but that will take a lot
> longer to convert than I planned and I need a fix NOW.
>
> I guess I am like all of the guys / gals who loved
> 4.5++ so much they held off upgrading to newer
> versions.  As it stands now I wish I was back in 98 /
> 6.1.
>
> Any help would be welcomed
> Marc
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus
>
>
>

Reply via email to