Programs do not launch, modboot.bat fails
Posted: Sun Jan 23, 2011 3:14 pm
I have a weird problem with UBCD for some days now on one of my machines. It used to work. Now it doesn't. The problem is that whatever I choose from the menu the launch of the program will eventually fail. Once I hit enter all the commands that seem to be in _MODBOOT.BAT are echoed to the screen and run thru very quickly (which was not the case before, this is usually hidden). First on A:, then on Q: (ramdisk). Finally, that comes to an end asking (this is not literal) "pause MODBOOT: CTRL-C to abort, any key to skip/run 2peruse.bat". If I hit a key it runs thru more lines and then asks another question of this kind. And that goes on and on and on, until it finally says something about "skipping unpacking autorun3.cab" and throws me to the DOS prompt. This happens with every program and with every program startup option I try.
What's going on here?
I think it used to run a few weeks ago on that machine, but I'm not 100% positive. It runs fine on another machine were I tested the CD.
The only change to the hardware in the meantime was a BIOS update because the AMD virtualization support wasn't correctly working (the update fixed that). I disabled VT in the BIOS, but this didn't change the problem with UBCD.
The reason why I want to run UBCD is that I want to run Samsung ES-Tools from it to check a certain harddisk. SE-Tool *sure* used to work on that machine, but suddenly fails. It is stuck on the "Autodetection" line and I can't move the cursor to select a disk for diagnostics. So, the only thing it does when I hit the cursor key or enter is another quick autodetection. That's why I wanted to check if the ES-Tools on UBCD has the same problem.
What's going on here?
I think it used to run a few weeks ago on that machine, but I'm not 100% positive. It runs fine on another machine were I tested the CD.
The only change to the hardware in the meantime was a BIOS update because the AMD virtualization support wasn't correctly working (the update fixed that). I disabled VT in the BIOS, but this didn't change the problem with UBCD.
The reason why I want to run UBCD is that I want to run Samsung ES-Tools from it to check a certain harddisk. SE-Tool *sure* used to work on that machine, but suddenly fails. It is stuck on the "Autodetection" line and I can't move the cursor to select a disk for diagnostics. So, the only thing it does when I hit the cursor key or enter is another quick autodetection. That's why I wanted to check if the ES-Tools on UBCD has the same problem.