Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
My application causes PC lockup
Message
From
13/01/1999 01:35:30
 
 
To
12/01/1999 00:50:51
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00174939
Message ID:
00175349
Views:
32
Hi Cetin & Nigel,

Thanks for the replies. The problem seems to be triggered by printing, usually by the 3rd or 4th iteration. However the printer drivers work flawlessly for all the other apps, as well as my app. The computer generally freezes after that on a menu selection. The Printers are HPIII-HP4000T and are fairly standard.
The only difference between the machines with the problem and those without is that the ones with the problem have Ethernet cards and the others are using Madge Token Ring cards.
Today I tried downloading and installing the MS service patch 1 and the Y2K VFP patch, used the setup wizard, used the results to reinstall the app - no difference.

Nigel, I do not have the Client 32 version info.. However, as mentioned above, the problem seems to center around the site using Ethernet cards vs Token ring. The problem occurs only with my app (deep sighs!).

Another joyful tidbit I received today... One of the users claimed index error problems with another totally unrelated database (not of the xbase variety) when it's app was being run alongside my app.

Seems my VFP app is corrupting memory until it finally locks up the PC.
Libraries used : Jkey & GPlib.

:(



>>Help!
>>I have an multiuser application in VFP6 in a Novell 4.01 environment running on PCs with Windows 95b installed. Most PCs seem to run the application fine, 3 so far lockup (require power off/on) whenever they go through about three iterations of executing a module which prints a report. They typically lockup at the menu selection and never on the first try. I have reinstalled Windows and the application from the ground up and that has not cured the problem.
>>Any suggestions, anyone?
>>
>>TIA
>Ashley,
>Check the printer drivers they're using. Some HP and Epson are known to be problematic. Try to use drivers that ship with win.
>Cetin
Previous
Reply
Map
View

Click here to load this message in the networking platform