I'm having problems with the F-50 driver on Windows 98, and following this thread have installed the latest beta of Sveta and the beta F-50 driver.
The configuration program does not detect the player, although it appears as MPMAN F50 USB Driver in the device manager, and the 'official' MPMan manager can see it.
The logfile shows the following:
Opening MPMan Driver
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
Trying Registry Open MPMan Driver
MPMan Trying Driver Open '\\.\0000000000000007#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000007#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000008#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000008#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000009#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000009#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000d#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000d#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000007#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000007#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000008#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000008#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000009#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000009#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000d#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000d#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000007#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000007#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000008#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000008#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000009#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000009#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000d#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000d#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000007#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000007#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000008#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000008#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000009#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\0000000000000009#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000d#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000d#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
MPMan Trying Driver Open '\\.\000000000000000e#{e79d6fe0-7e5d-11d4-a9ee-0050da8c6909}': Opening: Wrong VID PID
Open MPMan: Fail
The same drivers, player and version of Sveta works fine on another PC with Windows XP installed.
That is odd, the 'open path' should contain a VID of 0a62 and PID of 0004 for F50, I am thinking if the above is correct (for Winodow 98) then it does not have that, but 00000000000e# feels wrong to me...
I need to find a machine with Windows 98 and USB, if you could drop me an email and I will create a different dll you can try:
Comment