I'm sure this question has been posed before but I'm struggling to achieve the result I'm after.
At present, I'm attempting to create an image file from the file contents of a floppy disk/diskette and the program I'm using - called ubeedisk - to achieve that requires incorporating the executable as part of a long command line, comprising hyphens, equals signs, switches and parameters, into the Windows XP Command Processor.
If I use cmd directly and correctly enter the command line switches/parameters - or a batch file containing them - I have complete success. However, my typing is becoming poor and there are a lot of possible variations in the command line, which could result in the creation of numerous batch files if I adopt that approach, so I've now written a VB program that will create the appropriate batch file for me each time and, hopefully, run it directly. I would like to be able to produce the image from within my program so the Shell function seems the obvious way of doing it. (I've never mastered APIs, so I would prefer to stay away from them if possible).
I keep all my VB programs on my E: drive in a folder entitled 'John's VB5.0-VB6.0 Programs' and the program I've written is in a sub-folder, called 'Floppyio'. The ubeedisk executable in the batch file - named ReadDiskToImage.bat - is located in a folder of the same name which is in 'Program Files' (on the C: drive). The cmd executable is, of course, in the system32 folder in the Windows folder. All rather confusing perhaps. The filepaths of both ubeedisk and the image file, as well, of course, as the files themselves, are enclosed in quotes in their respective positions in the batch file.
Finally I need to be able to see what is happening in the command processor throughout the operation because ubeedisk asks the user to press the 'dot' key and then press 'Enter' for the operation to begin to read the disk and to eventually produce the image. With direct entry into cmd, ubeedisk works extremely well and I have no complaints in that regard but being able to replicate that in my own program would make matters a lot easier for me. (There are other operations besides creating images from disks but once I have mastered that one, hopefully all the others will require a similar approach. I have already incorporated them in my program and produced corresponding batch files).
Here's hoping someone will come up with a way to make it work. Thanks for any assistance.
At present, I'm attempting to create an image file from the file contents of a floppy disk/diskette and the program I'm using - called ubeedisk - to achieve that requires incorporating the executable as part of a long command line, comprising hyphens, equals signs, switches and parameters, into the Windows XP Command Processor.
If I use cmd directly and correctly enter the command line switches/parameters - or a batch file containing them - I have complete success. However, my typing is becoming poor and there are a lot of possible variations in the command line, which could result in the creation of numerous batch files if I adopt that approach, so I've now written a VB program that will create the appropriate batch file for me each time and, hopefully, run it directly. I would like to be able to produce the image from within my program so the Shell function seems the obvious way of doing it. (I've never mastered APIs, so I would prefer to stay away from them if possible).
I keep all my VB programs on my E: drive in a folder entitled 'John's VB5.0-VB6.0 Programs' and the program I've written is in a sub-folder, called 'Floppyio'. The ubeedisk executable in the batch file - named ReadDiskToImage.bat - is located in a folder of the same name which is in 'Program Files' (on the C: drive). The cmd executable is, of course, in the system32 folder in the Windows folder. All rather confusing perhaps. The filepaths of both ubeedisk and the image file, as well, of course, as the files themselves, are enclosed in quotes in their respective positions in the batch file.
Finally I need to be able to see what is happening in the command processor throughout the operation because ubeedisk asks the user to press the 'dot' key and then press 'Enter' for the operation to begin to read the disk and to eventually produce the image. With direct entry into cmd, ubeedisk works extremely well and I have no complaints in that regard but being able to replicate that in my own program would make matters a lot easier for me. (There are other operations besides creating images from disks but once I have mastered that one, hopefully all the others will require a similar approach. I have already incorporated them in my program and produced corresponding batch files).
Here's hoping someone will come up with a way to make it work. Thanks for any assistance.