Actually, you have raised a good question. Most of the fixes I have done apply to
both NT and 98 as far as I know. The exception to this is the PathExt stuff (The 
registry stuff is ok, I believe) and the behaviour of 'SET' (On NT, SET C lists
all vars starting with C, on 98 it looks for a var 'C'). In an ideal world,
wcmd should behave as 98 if 98 emulation is required, and NT if the extensions are
required. However, the 98 stuff is (Mostly, except set!) a subset of the NT stuff.
Any ideas how to handle this?

I must admit, doskey emulation would be very much appreciated - Any ideas how
to capture PF1, PF3 and PF8 (and provide a history!)? If someone points me towards
how, I'll have a play.

Incidentally the reason I was trying to get this working was a batch program
which set some env vars, launched a Object Rexx program which in turn launched
a C program (which also ran other things). I found system("dir") didnt work
and worked from there. My rexx program is stuck now as ORexx launches a background
process and IPC doesnt seem too good (No syncronization) - My next debugging step!

It is worth pointing out with my new patch, you can set comspec to wcmd.exe
(I had to do a copy of wcmd and call it wcmd.exe...) and a simple C program
which uses the system() command now works. I am not sure if we should consider
making this part of wineinstall or not. Perhaps in the future?

Jason



____________________________________________________________
Freeserve - get your free ISP service including web-mail at:
www.freeserve.co.uk




Reply via email to