Problem running 16 bit DOS app on Win2k

Executioner · Post by **Executioner** » Tue Apr 16, 2002 3:16 pm

I'm here at work, and they upgraded our machines to Win2k on NTFS file system. We were using Win95b. I have a program called Calibration Manager, which is a DOS program. After upgrading to Win2k, the program runs, but when we try to write to the hard drive, we get this error:

16 bit MS-DOS Subsystem
An application has attempted to directly access the hard disk, which cannot be supported. This may cause the application to function incorretly. Choose 'Close' to terminate the application.

The options available are 'Close' and 'Ignore'. Selecting either one caused the program to terminate.

I'm able to bypass this problem by having it write to a floppy disk, but it's not what I want. After reading several posts on Google, it sounds like there is no way around the direct access by old applications, but someone mentioned about a hack, but did not really discribe this hack. Anybody have any ideas on this?

leerus · Post by **leerus** » Tue Apr 16, 2002 11:50 pm

Possibly create a FAT 16 partition on the hardrive to write to. That's about the only thing I can think of. Partition Magic should be able to perform this function for you.

May I ask, what does the program do and is it something someone at work wrote up or was it purchased?

Executioner · Post by **Executioner** » Wed Apr 17, 2002 12:37 am

The program keeps track of instruments that we calibrate here in the lab. We've been using it since 1992, and have 10,000+ records. It was written in Clipper language. The authors of the program are still around, and they have version 3.x which supports Win2k and XP, but it's a lengthly process I have to go through to get it installed. I have to "validate" the software first before it can be installed. We are regulated by the FDA, and if it's used for any quality related stuff (which encompuses Calibration), then it has to be validated before use. This also includes any software and even spreadsheet templates.

I really don't have the time to go through all these hoops yet. What is really funny is I have the new version. We (out lab) bought it back in 2000 with a 5 user license, but it just sits in our lab not installed because of the validation issue. The authors of the software said I'm lucky it runs at all on Win2k. I looked at the autoexec.nt and config.nt files, and noticed that the IS team here at work did include DPI support for DOS, and some other old DOS commands like files=50. My only issue was writting to the hard drive, but if I can write to a floppy, then that is my way around this problem until I can finally upgrade to a Windows version of the software.

The idea about using Partition Magic to create a small partition is probably out of the question. This is the companies pc, and I don't want to piss-off the IS guys by doing something that I'm not suppose to do. They are responsible for setting up and maintaining the machines. Their answer to my problem is a simple one: upgrade your software LOL. So I can't fault them for that answer.

EvilHorace · Post by **EvilHorace** » Wed Apr 17, 2002 5:43 am

It's my best guess that you'll need to install that newer version but do you have a specific tech hot line for that PC or that program that you can call for their input? With our leased company PC equipment, we have a specific support # and we let them make those kind of calls as otherwise it's our fault if we try something that's perhaps questionable and if that idea fails, it's a big hassle to get everything right again. For example (not exactly related but....), the last time a guy tryed updating the newest software (a guy who'ld never done it before), I think he botched something big time as the next day I hear "the servers HDDs NG" and a guy was sent over to replace it. It took a week and me getting upset, finally calling the support # myself before our networked PC "cart" was fully operational again. Doing PC related work there, like software updates isn't why I'm there, not my job (nor anyone elses technically) so it's always a hassle whenever it needs to be done every few months as everyone who's told to do it (trying to make it someones job) always passes the buck by ignoring it for as long as possible. The software has time limits on it though so it eventually becomes a problem until it's updated. Ahhhh, some of the joys of modern day life

leerus · Post by **leerus** » Wed Apr 17, 2002 12:43 pm

Ah yes, partisan politics in the IS dept. Hey guys, if you control the machine, then you control the software too. Sooo, you install and go through the calibration with the FDA or install a small second small hard drive on my system set to FAT 16 so we don't have to go through all of that crap. Ahh legacy programs, I love em!!!!!!!

Fortuantely where I work, that logic works......some of the time.

Does the machine have to be networked? Possibly an old puter sitting in the junk room can be installed as a dedicated DOS box for this? Probably already broached, but I had to ask.

TheSovereign · Post by **TheSovereign** » Wed Apr 17, 2002 1:51 pm

its simple the program is attempting to write a fat16 entry onto the hard drive
its old abandon the program or find a substitute

vwkess · Post by **vwkess** » Wed Apr 17, 2002 2:28 pm

The NT security model doesn't allow direct access to hardware; hence some old 16 bit DOS apps don't work. There are "drivers" or interfaces out there that do translate those calls. For example: http://www.direct-io.com/directio.htm

b-man1 · Post by **b-man1** » Wed Apr 17, 2002 5:57 pm

probably not the answer...but...

can you right click on the .exe or file you are running and select a different compatibility mode? perhaps a "Windows 95 Compatibility Layer" would do the trick?

.02

btw, what kind of lab are you in? if it's FDA regulated...must be a clinical or drug lab? i'm asking because i have a medical background...

Executioner · Post by **Executioner** » Wed Apr 17, 2002 7:47 pm

Thanks for the suggestions. At this stage I have some options:
1. Ask IS to create a 1 gig fat16 partition using Partition Magic.
2. Use my floppy drive for direct writting to the drive (which is my current work around).
3. Update the software.
4. Buy that device driver that vwkess recommended.

b-man1:
I'm a supervisor of a Calibration Lab internal to the company. I've been wtih the company for 15 years, and 25 years in the calibration business. Our company makes medical devices such as balloon catheters used in angioplasty. We also have a stent, the same one that was inserted into the vice president.

Our lab performs calibrations on a wide varity of instruments. We try to do 98% of them in house, and the rest we farm out to standard calibration labs. These are usually our standards. When I started with the company, we had only 400 instruments. Now we have over 10,000+ instruments. We add almost 100 new instruments per month. It keeps us very busy hehe.

leerus · Post by **leerus** » Thu Apr 18, 2002 12:02 am

Hmm, Executioner and you work for a medical device company creating those things we need to live.

I find that beautifully morbid.

EvilHorace · Post by **EvilHorace** » Sat Apr 20, 2002 10:05 am

True indeed but I'm sure they don't call him that at work

TruckStuff · Post by **TruckStuff** » Sat Apr 20, 2002 10:33 am

I might bit missing something here, bot how is creating a fat16 partition going to bypass NT's security procedures?