Software Support > DOS/WinCab
DOSCab/WinCab Jukebox 3.0 Beta 1 Released
johnman001:
If it is a sound card issue, then what could have happened between last night when it worked with the existing drivers and this morning when nobody used the computer.....
It's a simple AWE64 soundblaster card, so it should be a no-brainer....
johnman001:
After taking your advice and attempting to change my sound card configuration over and over and over and over with no luck, I was going to attempt more troubleshooting so I attached a standard mouse to the PS/2 port so it would be easier to work with (rather than the trackballs on the control panels), DOSCab now plays.
The trackballs on my cocktail cabinet are oddball devices (they are serial devices with PS/2 adapters that are plugged into USB/PS2 adapters). I am doing this so that under Win98, I can have player 1 and player 2 have seperate trackballs in 2 player games.
I only use the PS/2 mouse when troubleshooting or setup (I have a plug under one of the control panels that lets me plug a mouse and a keyboard in when required).
Now that I can duplicate the issue I am having, is there any way for DOSCab to work without having a mouse plugged in? I am assuming that the program is somehow looking for a mouse just prior to playing a song for some reason......
In a nutshell, it was not a sound card setup issue, but a lack of a PS/2 mouse issue.
Chris:
--- Quote from: johnman001 on November 21, 2004, 05:41:28 pm ---After taking your advice and attempting to change my sound card configuration over and over and over and over with no luck, I was going to attempt more troubleshooting so I attached a standard mouse to the PS/2 port so it would be easier to work with (rather than the trackballs on the control panels), DOSCab now plays.
<...>
Now that I can duplicate the issue I am having, is there any way for DOSCab to work without having a mouse plugged in?
--- End quote ---
My DOS test machine does not have any mouse drivers loaded. If you have mouse=DISABLED in the jukebox.ini, the mouse should never be checked at all.
Is it possible that the presence of the mouse is changing the IRQ on which your sound card appears due to Plug and Play? If there is a SET BLASTER line in your autoexec.bat, try REM'ing it out.... it may not have the correct info, and if it is not present the jukebox will attempt to autodetect the IRQ.
--Chris, still without his main PC
garyh:
Chris,
Sorry to hear about your hard disk crash, hope the rebuild is coming along okay.
You sent me a test version of WinCab to try with my touchscreen and I sent back a a reply but it may have gone down with your disk. Just to let you know that it didn't work. The cursor appears but touching the screen has no effect at all. The cursor doesn't move and "double clicking" has no effect. I am using 3M MicroTouch drivers and the touchscreen works fine with all other Windows apps.
I noticed that the file sizes of the .exe and .dll files you sent are exactly the same as the 3.0B4 versions, and the debug log header states it is 3.0B4 - is this what you would expect for the touchscreen test version?
Do you know what hardware / software the other touchscreen testers are using?
Best regards
Gary
Chris:
The DLL is the most important change. The correct version should have a Halloween date on the DLL file. Make sure you don't have any other alleg41.dll's running around anywhere.
--Chris
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version