Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Development on a special drive letter
Message
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00178297
Message ID:
00178924
Views:
34
Hi Dave,

>It was nice of them to provide the source code in those days; there was a smallish bug in GenPD too. I'm still using GenPd printing labels to Dot matrix at one site :-)

It was nice of them. The only thing I could never figure out was why on earth they would bother with a C library for communicating with the printer. While you could control whether or not the library was used because they supplied Fox code, I couldn't understand the point of the C library in the first place. Wait, I know, must of have a performance issue.*LOL*

>The I/O error wasn't nasty on DOS/Win3.1 machines because you could ignore it, but with the first NT Workstation and then Win95 it became a real show stopper for anyone with a CD. There's also a problem still on machines that don't have an A: drive but the BIOS sort of thinks there is one; like some IBM PCs. Funny how IBM have the least standard IBM PCs :-)
>
We've had more problems with IBM machines than any other. We've gone back and forth between manufacturers. The last time we used IBM was a nightmare.

>As for tmpfiles, I'm not convinced the line in Config is necessary at all. I've not used it since Foxbase or Foxpro 1.02 days. The tmpfiles directory always comes up as the local Windows Temp directory (Sys(2023)) in all current versions of Foxpro. (But I think we've been thru this before :-)

Ah, but it is necessary. I mentioned that I was too embarassed to tell the story of why and how I managed to have this problem myself. Well David, it was all your fault!< gd&r >. When you and I previously had this discussion, in experimenting I elminated the TMPFILES line from my config file. Problem was that stupid here (me) forgot to put it back. No problem, except that my windows temp file directory was on my D: hard drive. Whoops! Naturally, when I turned some modifications over, all of a sudden I started getting calls about the I/O operation failure problem. The system, BTW, was five years old, and was rock solid. Anyway, in poking around the project table I discovered both the reason and the solution. Moral: Never make assumptions when you can be 100% certain that you can keep a problem from occurring with one simple line.

Regards,
George

Ubi caritas et amor, deus ibi est
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform