Re: Difference? (dos and registry)

["Matt Kettler" <Mkettler@Evi-Inc.Com>]

> ONE THING REALLY SUCKS- is you cannot make true DOS apps using C++
> Builder. I wanted to write a program last time that was a TRUE 16 bit DOS
> app that wrote and read from the registry. Fat chance on that one- but I
> ponder on how other companies do this... I know it can be done....
> 
> Chris Winters

Any *true* 16bit DOS app (one which can run under plain dos, or 
win95's "DOS mode") which is accessing the registry would have to do 
so via directly reading and writing the registry file itself using 
such functions as fread() and fwrite(). In DOS mode win95 
provides no win32 API services at all, including those for writing 
the registry.

That aside, 16bit DOS apps , which needn't be true dos 
apps ( and no I don't mean win32 console apps) can communicate with 
VxD's in the windows system via interrupt 2F. However  they won't work
properly unless run under a windows dos box, and will not run in 
win95/98's "DOS mode", since in that mode there are no VxD's to talk 
to. Even at that, I'm not sure what, if any VxD services for registry 
entries are available over the int 2F interface. Most of those 
interfaces go out over DeviceIoControl as I recall.

My question is if you are working with the registry, you have to be 
on a win95/98/NT box, and not a win3.x/plain dos box.. so why not use 
a win32 console app? They can directly use win32 API services, etc and 
run in dos boxes under windows.. 
	Also, why would you want to build a true dos app under C++Builder, 
instead of Borland C++ 5.x? 99.9% of VCL will not, and can not ever 
work from a true dos app, so the point of using C++Builder is totally 
lost. BC is the natural choice for DOS, either that or watcom, MSC, 
etc. C++Builder is a windows development tool, for.. gee.. windows 
development.