Running Clipper 5.2e in Windows XP 2

[Balarao]

I just migrated to Windows XP and I am planning to run my Clipper program in that environment, however I keep getting an error whenever I open too many files.

When I am using Windows 98, I just place a shell in my config.sys and everything is ok.

Config.sys
shell=c:\command.com/p/e:1200

How will I include this line in Windows XP or is there a way around it. Windows XP is not that adept in handling dos programs.

Thanks in advance for your help.

God bless,

Balarao

 

[TonHu]

This is a golden oldy, comming from Windows NT as wel: put the Files=151 statement in config.nt, usually in your windows\system32 directory. Environment settings (clipper=E0;F151) should be put in the autoexec.nt in the same directory. (For some systems it's winnt\system32)

If you had done a search in this forum you would have found it more than once.

Windows XP is not very DOS-program friendly, but neither was NT or Windows 2000, so all your troubles wil have an answer but may be related to Windows 2000 or NT instead of XP. Try searching for Windows XP or Windows 2000 (W2K) and you wil find many solutions, for problems you haven't even encountered s-)

HTH
TonHu

 

[JockMullin]

Hi, Balarao

TonHu is bang on as to why your problem is happening.

However, to set environment variables in XP:

- Right click on My Computer (Either in START or on desktop.)
- Click on Properties
- Click on Advanced Tab
- Click on Environment Variables button
In there you can add/edit evironment variables which will apply to all DOS sessions.

For unknown reasons XP does not seem to use autoexec.nt, though it is there in SYSTEM and also in I386.

Jock

 

[Balarao]

Many thanks to you Jock!

Problem solved. You made my day!!!

God bless,

Balarao

 

[Bozz]

TonHu,

Is the Clipper=E0 still needed. I read recently that the problem that fixed has long gone, it might even have been a 87 bug.

Ian Boys
DTE Systems Ltd

 

[TonHu]

Ian,

If I leave it out, and try to reindex a large database with DBFNTX drivers I still get corruptions. As I dislike 'strange behaveour' in my apps, I keep this setting just to be sure I could (or should?) have put it inside my Blinker script, but I'd like to keep it external.

Thnx,
TonHu

 

[Bozz]

If it hurts don't do it! The only reason I asked was that I've included to for the last 15 years but then it was poo pooed by someone so I've taken it out recently. I might stick this one up on the news groups for some more opinions.

Ian Boys
DTE Systems Ltd

 

[TonHu]

AFAIK, the EMS bug thats circumvented by this setting was never removed from Clipper 5.2e, and thats the *only* stable Clipper-version that I know of :-( (I do own 5.3 + patches, but can't live with the unstable nature of it)

HTH
TonHu