| ??? 01/27/03 14:18 Read: times |
#37405 - RE: sending hex to com |
Donald......
Maybe I have some issues with my Win 2000 installation here. What happens for me is whenever I try to run certain 16-bit DOS type software, such as the aforementioned HEX2BIN utility, the program does work and produce the desired file conversion. The problem is that the program will start up and then there will be a delay of a significant length (I'm talking a delay of up to 20 or 30 seconds) while the OS does something. After the delay then the program runs and completes. I have no idea what is going on during this delay but I can say it makes putting certain programs in a Make type batch file a huge pain if you are in the Edit, Compile, Download and Debug cycle for any length of time. I have several Win 2000 systems, my Gateway development machine, an IBM 600E notebook, and a customer target embeddded machine with a 333 MHz SBC, all of which exhibit this strange phenomenon. If anybody else out there knows more about this issue please lets talk about it. Michael Karas |
| Topic | Author | Date |
| sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com | 01/01/70 00:00 | |
| RE: sending hex to com - Hyperterm | 01/01/70 00:00 | |
| RE: sending hex to com - Hyperterm | 01/01/70 00:00 | |
RE: sending hex to com - Hyperterm | 01/01/70 00:00 |



