DOS vs. Registry problem

[WinKrushR]

Problem when I try to run certain DOS programs (self-expanders, etc.):

Warning window shows up:

Title: 16 bit MS-DOS Subsystem

Message: ~program path~ SYSTEM\CurrentControlSet\Control\VirtualDeviceDriv ers. VDD. Virtual Device Driver format in the registry is invalid. Choose 'Close' to terminate the application.

Two Buttons: Close Ignore

Hm...On the self-extractors, installers, and some others if you hit 'ignore' the program will continue with no crashes, etc. Sometimes it'll bring down the program. Never crashes the system. Any idea? I'm going to hit TechNet but figured I'd drop a line here first.

Thanks

------------------
"What would anybody want with a blind dog?"

[wbatten]

Are you running Win2K? No DOS base applications is compatable with Win2K!

------------------
Techno®

[iateyourcat]

I wonder why those dos apps would be trying to access the hardware directly..

What are you expanding? zip/rar expanding or something else?

I've got one REG_MULTI_SZ value in that VDD key and it's a symantec antivirus dll.. prolly needs "low" level access to lock infected files.

..and dos apps do run in w2k, that's what NTVDM is for..

[This message has been edited by iateyourcat (edited September 20, 2000).]

[WinKrushR]

most of the time it's self-expanding installation programs. dunno why they'd be affecting hardware. I guess they're trying to write directly to the disk, and I've got an NTFS partition, perhaps?!?!?

/.confusion

[wbatten]

Let me make it a little plainer, in regards to using DOS base applications,

The disk operations are actually handled by the Windows NT Virtual DOS Machine (NTVDM), which is a 32-bit program, not by the MS-DOS emulator (Ntdos.sys). The interrupt 25h and 26h handlers do not call the functions that take care of the physical disk operation.

Wayne


------------------
I use The best program that cures Windows problems, Far more reliable than Norton Utilities, It's called FORMAT C:............Techno®

[WinKrushR]

Okay, the explanation is great, but what can we do about it? Is everyone having this problem when they install stuff??? Are you saying its a fault with the way the NTVDM handles these programs? If so, what about either a workaround or something? It's wonderful to know why, but I'd love to see something fixed. I'm not going to call M$ about it for another week, mostly because it took one of their MCSEs 2 weeks to figure out the prob. with my dual-boot system.

[wbatten]

I have not had this problem at all with Win2K! what program are trying to install? and I can try and install it, to see if the same thing happens to me!

Some expanders try to utilize native DOS that access interrupt 25H and 26H, this wont happen in Win2K, Some programs are NOT compatable with NTFS only the FAT file system.

------------------
I use The best program that cures Windows problems, Far more reliable than Norton Utilities, It's called FORMAT C:............Techno®

[This message has been edited by wbatten (edited September 21, 2000).]

[WinKrushR]

One of the programs is our proprietary Computer Aided Dispatch and Records Management programs. I'm reporting the problem to the developer's R&D.

It's had some problems with self-extractors. This is mostly in the form hardware drivers. Ex: the PCL drivers for a LaserJet 6L from HP for Win2K. It gave the error and then proceeded to expand correctly.

I'm reporting it to M$ today sometime. They'll probably have me send error logs and whatnot, but if it helps...