Solved

Old MS-DOS software needs to read/write data into 3.5" floppy disks.

Posted on 2013-11-28
4
490 Views
Last Modified: 2013-11-28
Hi EE,

I still use a very old software (20 years now) that runs via MS-DOS command prompt. The software is not commercially available and since then it was not updated for Windows
platforms.

In order to run the program nowadays I have first to plug an 3.5" external USB floppy disk drive to my PC. This is so because once that I run the program it automatically writes and retrieves data in or from the floppy disk at intervals depending on the process.

One relevant information is that the MS-DOS software asks for a floppy disk with a specific volume name (Mydisk123).

I have been wondering if there is a way to avoid the use of 3.5" floppy disks.

For example: is there a way to configure a USB port as the "A" drive, and have a USB memory plugged there, so that when the program wants to read/write on drive "A" it does it on the USB memory?

As explained above, I don´t have the means to reach the person that 20+ years ago wrote the source program and compiled it into an exe file.  

Thanks.
0
Comment
Question by:capterdi
  • 2
4 Comments
 
LVL 30

Accepted Solution

by:
pgm554 earned 500 total points
ID: 39684020
0
 

Author Closing Comment

by:capterdi
ID: 39684037
Great!

Three options to choose from.

Thanks.
0
 
LVL 43

Expert Comment

by:Steve Knight
ID: 39684220
If it does just want an A: drive just change the drive letter allocated to your usb key or create a small hard drive partition and allocate i that drive and name.

you may also want to consider dosbox or running it in 'winodows xp mode' -downloadable which is microsoft virtual pc running preconfigured win xp, or using vmware player say.  with those you can map  a floppy drive,  cd etc. to a file instead.

good luck with it, find this sort of thing a lot with lots of older companies unwilling to let the old stuff go.
0
 

Author Comment

by:capterdi
ID: 39684223
Thank you dragon-it.
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

The following is a collection of cases for strange behaviour when using advanced techniques in DOS batch files. You should have some basic experience in batch "programming", as I'm assuming some knowledge and not further explain the basics. For some…
VALIDATING DATES One method of validating dates is to jam the date into the DATE command and see if it accepts it by examining the system's errorlevel value. A non-zero result indicates failure. A typical example might look something like the fol…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now