Author Topic: Puzzling Issue (Read 16791 times)

canadien37 · « **on:** January 15, 2007, 03:13:40 pm »

Hi guys,

I am having an issue that is making me scratch my head.....I started having trouble getting my Music Keg to work...
It was working fine until a few days ago, when I added some songs to it. Went to put the DMS back into car and my radio displayed Disc, then AUX...I upgraded to Media Manager 3.92, formatted the PHTSYS partition(did not delete it), extracted the firmware from your website to that partition, checked with DMS doctor, got a message(failed system test, could not load XML document)...all other tests were ok. Then, I re-formatted the partition, used Media Manager to install firmware, checked with DMS Doctor again...it failed the system test again...This time the message is:"Could not find system file H:\<!DOCTYPE..." I covered as many of the basic troubleshooting steps I knew.. Hope you can help. FYI, I have a Kenwood HU also.....

canadien37 · « **Reply #1 on:** January 15, 2007, 03:38:40 pm »

Just a little more info....I did a search on thew PHTSYS partition and found two .XML files: CurrentSetup.XML, and Properties.xml.....hope addtional info gives a clue as to what's happening here.....

judb · « **Reply #2 on:** January 15, 2007, 04:42:53 pm »

when you reload the firmware after clearing the phtsys partition dms doctor will fail like that till you run PMM once, it creates the needed files.

however, phtsys isn't where any playlist data is stored, so adding songs messing it up would mean you need to clear out the phtdta\profiles\default folder most likely. then you'll have to recreate your playlists but the music copy wont have to happen again so it should be fast.

try that and see what happenes.

canadien37 · « **Reply #3 on:** January 16, 2007, 03:09:38 pm »

Thanks for that, I will try your suggestion.....what do you mean by running PMM will recreate the file? does that mean just loading it(PMM I mean) or doing something else with it?

canadien37 · « **Reply #4 on:** January 16, 2007, 03:23:28 pm »

ok, I closed PMM, cleared that folder you suggested, ejected the DMS, reinserted the DMS, PMM started and my playlists are still intact...
Is this the way it should be?

judb · « **Reply #5 on:** January 16, 2007, 06:16:39 pm »

you can try re-ejecting the DMS from PMM and see if it helps.. if not, i suggest going into PMM and either deleting your playlists (but not the media if prompted) and then recreating a single one with a few songs and then ejecting the DMS again. See if that works.

PMM keeps some data in some database files on the DMS that may be where the playlist data is pulling from. you can delete them as well if you would rather go that route.

The .db .idx .dat and .xml files in the root of phtdta and in the profiles folder are also used to store that data.

canadien37 · « **Reply #6 on:** January 17, 2007, 03:58:45 am »

ok, I did as you sugggested, deleted and recreated my playlists, ran PMM again, when I check with DMS Doctor, I get same result as before(the description in my first post). Also the same result happens(as in first post) when the DMS is installed in my Keg. I'll tell ya, I'm a tech, but this thing has me baffled...Any idea what system file it is looking for? Apparently it will not boot in my Keg.

judb · « **Reply #7 on:** January 17, 2007, 04:41:42 am »

it may say in the errorlog on the PHTSYS partition...
can you give me a dir listing or a screenshot of explorer with all the files in PHTSYS root dir showing?

lastly, do you have a plugin folder? try renaming it and see if that helps.

canadien37 · « **Reply #8 on:** January 17, 2007, 04:11:46 pm »

I cannot send you a screenshot, I was unable to attach a picture....

judb · « **Reply #9 on:** January 17, 2007, 05:07:51 pm »

you can upload one to something like imageshack and then link the image using the img tags.. or you could open a command prompt and go to that drive and do a:
dir > c:\phtsysdir.txt
then open that file in notepad and cut n paste the text into a post.. make sure you use the code option around it so no formatting occurs. The code option looks like a # sign button when you create a post.

canadien37 · « **Reply #10 on:** January 18, 2007, 04:58:14 am »

ok, here is the list......

Code: [Select]

 Volume in drive C is Windows XP Professional
 Volume Serial Number is C0A8-1CFA

 Directory of C:\Documents and Settings\Donald Hicks.DON-YVLWAU2NPIP

01/17/2007  11:33 PM    <DIR>          .
01/17/2007  11:33 PM    <DIR>          ..
06/15/2002  11:40 AM    <DIR>          .java
12/08/2003  07:48 PM    <DIR>          .jpi_cache
06/24/2002  02:40 PM               686 .plugin140.trace
06/23/2004  08:49 PM            16,311 ActiveTaskLog.html
09/09/2003  03:51 PM                 0 AdobeWeb.log
10/10/2006  06:17 PM                41 ajmf.dat
06/13/2006  03:41 PM    <DIR>          Contacts
12/10/2006  12:51 PM               131 default.pls
01/17/2007  11:16 PM    <DIR>          Desktop
01/05/2007  10:26 PM    <DIR>          Favorites
11/10/2006  09:16 PM    <DIR>          Incomplete
01/10/2007  10:22 PM    <DIR>          My Documents
01/17/2007  11:33 PM         9,961,472 ntuser.dat
06/06/2003  10:22 AM             1,749 plugin131_06.trace
10/18/2005  11:22 PM               870 resetlog.txt
06/03/2004  08:41 PM    <DIR>          SecurityScans
11/10/2006  09:13 PM    <DIR>          Shared
12/18/2006  11:00 PM    <DIR>          Start Menu
12/20/2006  10:30 AM    <DIR>          temp
12/08/2003  07:54 PM    <DIR>          WINDOWS
07/10/2005  09:54 AM            84,501 WinPatrolLog.html
               9 File(s)     10,065,761 bytes
              14 Dir(s)  236,525,015,040 bytes free

I hope this is what you wanted, this does not seem to show the files in H:\PHTSYS........

judb · « **Reply #11 on:** January 18, 2007, 05:13:14 am »

You have to type the drive letter first before doing the dir command

so if it is your H drive you would type
h:
dir > c:\blah.txt

canadien37 · « **Reply #12 on:** January 18, 2007, 02:56:37 pm »

Code: [Select]

Volume in drive H is PHTSYS
 Volume Serial Number is 0403-4D2E

 Directory of H:\

01/17/2007  11:15 AM               267 phatman.ini
04/07/2003  02:47 PM           162,564 phatwma
10/21/2004  11:37 AM               244 oggplay-la.sig
06/13/2002  02:51 PM           389,875 Welcome to PhatNoise.mp3
06/13/2002  02:13 PM                24 WelcomeFileName.txt
06/13/2002  02:13 PM                59 WelcomeFileText.txt
10/27/2000  12:16 AM                11 blank.bif
07/01/2003  10:58 AM               238 blank.sig
01/17/2007  09:17 AM                 0 forcesettings
02/03/2003  11:20 AM                 0 forceupdate
10/30/2002  02:19 PM            41,936 hdparm
07/01/2003  10:54 AM               239 hdparm.sig
12/07/2004  04:18 PM           819,252 linux
12/07/2004  04:56 PM               242 linux.sig
01/17/2007  11:15 AM            24,513 phatbox.ini
06/12/2002  04:47 PM            26,866 pkeys2.e
10/21/2004  11:37 AM               239 pkeys2.sig
10/04/2004  07:55 PM             2,880 pkeysa.e
10/21/2004  11:37 AM               243 pkeysa.sig
10/15/2002  12:15 PM               114 playloopfile
10/21/2004  11:37 AM               246 playloopfile.sig
12/07/2004  04:18 PM           409,600 ramdisk
12/07/2004  04:57 PM               238 ramdisk.sig
11/07/2001  02:55 PM                71 rc.sh
12/07/2004  04:56 PM               246 rc.sig
04/07/2003  02:42 PM           819,180 RoyalLin.ux
04/07/2003  02:42 PM            25,040 swgrli
10/21/2004  11:37 AM               238 swgrli.sig
01/17/2007  09:16 AM    <DIR>          images
01/17/2007  09:16 AM             1,149 CurrentSetup.xml
01/17/2007  09:08 AM    <DIR>          Data
01/17/2007  09:08 AM    <DIR>          TTS
10/21/2004  11:37 AM               246 progpld.sig
03/03/2004  07:52 PM           187,600 51d
10/21/2004  11:37 AM               244 51d.sig
10/20/2004  03:43 PM               349 exec.ini
10/21/2004  11:37 AM               239 exec.sig
10/01/2001  02:14 PM           343,260 phat
12/07/2004  04:18 PM           197,616 phatd
12/07/2004  04:57 PM               237 phatd.sig
10/30/2002  03:19 PM            15,536 progpld
12/07/2004  05:20 PM             3,832 properties.xml
10/05/2001  01:13 PM               743 boot5.pac
07/01/2003  10:58 AM               240 boot5.sig
10/16/2001  11:40 PM               735 boot.pac
07/01/2003  10:58 AM               243 boot.sig
10/20/2004  06:55 PM             9,975 firmware.pac
10/21/2004  11:37 AM               236 firmware.sig
10/10/2003  01:30 PM             5,013 KWMK_logo.gif
03/07/2002  05:53 PM             5,498 prog.bif
07/01/2003  10:58 AM               236 prog.sig
10/21/2004  11:37 AM               239 phatwma.sig
10/04/2004  07:55 PM           110,000 aadec
10/21/2004  11:37 AM               244 aadec.sig
01/17/2003  12:24 PM           102,912 flacplay
10/21/2004  11:37 AM               239 flacplay.sig
10/19/2004  04:42 PM                48 needaac
10/21/2004  11:37 AM               243 needaac.sig
06/30/2003  05:12 PM            92,512 nmp3
10/21/2004  11:37 AM               244 nmp3.sig
08/18/2003  12:07 PM           488,632 oggplay-ha
10/21/2004  11:37 AM               241 oggplay-ha.sig
08/18/2003  12:07 PM           458,328 oggplay-la
              60 File(s)      4,751,774 bytes
               3 Dir(s)     262,582,272 bytes free

ok, sorry about that, geez, darn DOS commands, guess I have to dig out the old knowledge..hehe.

judb · « **Reply #13 on:** January 18, 2007, 07:36:49 pm »

I'll look at my file list when I get home.. but at first glance it looks okay.

I'd delete the forceupdate and forcesettings files because that makes the box try to update the 8052 software which takes like 5 minutes to complete. Unless you want to put the drive in and wait 5 minutes to see if it works or not.

judb · « **Reply #14 on:** January 18, 2007, 07:41:22 pm »

On second thought, I strongly suggest leaving those files there and making sure to wait till the firmware update is complete. if the green light flashes steady for more than about 20 seconds it is likely doing a firmware update.. if the rate of blinking changes or stops it is an error code due to drive / software issues.

canadien37 · « **Reply #15 on:** January 19, 2007, 03:48:11 am »

I installed the DMS into the Keg, waited 10 mins., turned radio on, display said "Disc" then "Aux"....I think it's a software issue, there was no error log in my list to explain why there is difficulty reading the system files in PHYTSYS...I'll tell you, puzzling....I can do anything I want while DMS is in cradle, add songs, delete, configure playlists, eject DMS, etc., but it will not boot in the KEG....I must have installed the firmware several times, hoping to get the system files installed....to no avail....I even formatted both partitions and started from scratch, nothing different.

canadien37 · « **Reply #16 on:** January 19, 2007, 03:51:33 am »

I didn't address the light situation in my last post....because of the way the unit is mounted in my trunk, it is very difficult to see the lights without unmounting it.

sbingner · « **Reply #17 on:** January 19, 2007, 07:20:40 pm »

When you reformatted your PHTSYS (H:) -- did you format it as FAT32? If not, it might work in windows but not on the PhatBox

canadien37 · « **Reply #18 on:** January 20, 2007, 03:19:57 am »

yes, it is FAT32.....

judb · « **Reply #19 on:** January 20, 2007, 04:12:43 am »

try making a copy of the file properties.xml and naming it bootload.log ... stick it in the keg and give it a minute or so. then shut the radio / car off and wait another minute or so then pull your drive.

Pop the drive in and open the bootload.log in notepad and see what it says. post the 7 lines for us. (shouldn't be much at all in it..

Code: [Select]

BOOT0-0: OK
BOOT0-1: OK
BOOT0-2: Successful
BOOT9-X: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful

as an example thats what a good bootload.log looks like

News:

Author Topic: Puzzling Issue (Read 16791 times)