maxence wrote:Hi TvE,
Ugh, that dreaded popup dialog again. For your information, this dialog is triggered by Java/Windows when the app is trying to access a drive that has no media in it, such as a floppy or CD/DVD drive.
I have a few questions for you if you don't mind :
1) Does the same dialog popup with muCommander 0.8 ?
2) How many times do you get this dialog on startup, just once ?
3) Do you also get this popup dialog after the app is started ? If yes, can you specify what you did to trigger it ?
A temporary workaround would be to disable the floppy and/or CD/DVD drive on the computer if you're not using it. I think you can do that by right-clicking on the drive's icon in Windows Explorer.
This morning I am capable of launching muCommander on both my Windows XP machines (They have been rebooted a couple of times since this error report that might influence the performance)
The Thinkpad X60 (that have no drives) can now launch both 0.8 and the nightly build.
The HP Compaq d530 CMT (that DO have optical+floppy drives) can now launch the nightly build but 0.8 still throws the error.
- It does so only once and I can hear a Click from one of the (floppy?) drive right after launching the app...
There might be something else wrong (this should probably go to a new thread) I am unable to activate the menus using the standard Windows way. EG You have underlined the F
in the File menu and that indicates that one should be capable of displaying this menu by hitting ALT-F on the keyboard (unfortunately a place where Mac OS X is worse keyboard-shortcut-friendly-wise than Windows ).
I expect this to be working in an application that so heavily enforces the use of the keyboard
PS.: Both my PC's and both the nightly build and 0.8 build acts this way