PhatHack DMS Tools Doesn't See DMS Cartridge

[kbaradet]

System: Windows XP SP2
Symantec AV v10 installed, but disabled.

Hard Drives: C: and D:

DMS Cartridge seen by Windows as  PHTSYS is E: &  PHTDATA is F:
Cartridge is an unmodified 20GB from Audi Phatbox w/ 7.02 firmware
PhatBox is unpatched.

PhatNoise DMS Doctor passes all test up to the "Checking System Files" where it fails with a "server name or address could not be resolved"

PhatNoise Media Manager 3.92 is able to see the DMS

Start PhatHack DMS Tools 2.10 and it immediately reports that no DMS is found

Next tried DMS Utils 1.2.1, it fails when running backupdms.bat in the following manner:
     ***************************************************************
     Please insert stock (original) DMS And make sure that the
     DMS drive letters are seen for PHTSYS and PHTDTA in explorer
     ***************************************************************

     Press Enter to Continue when ready


     ***Rescanning Connected Disks***

     ***Rescan Complete***

     ***Determining if new DMS drive is seen***

     Testing disk 2 (19 GB)
     * Volume 3         PHTSYS       FAT32  Partition    260 MB  Healthy
     Error: PHTSYS has no drive letter assigned, assigning
     Error: unable to assign partition, bailing out

Any suggestions as to what to try next?

Thanks,
Kevin

[VorTechS]

Can you mail me your Log files under My Documents\PhatHack Media Manager\Logs and I'll take a look see what might be causing the problem.

[kbaradet]

It appears that the combination of the USB hub chipset in the computer, the DMS cradle and software don't play nicely most all of the time. PhatNoise Media Manager also had a hard time reading the DMS ID from the disk 9 times out of 10.

I ended up using another computer and the PhatHack DMS tools successfully ran.

Thanks for the tools.

Kevin

[VorTechS]

It would still be nice to see the log files, as the tools use WMI to query the disc, it may well be that the chipset is reporting additional data elements that need to be eliminated from te WMI queries.

Glad it all worked out in the end.