Author Topic: incorrect volume labels  (Read 11506 times)

0 Members and 1 Guest are viewing this topic.

Offline dark_gable21

  • Newbie
  • Posts: 6
  • PhatHacker
incorrect volume labels
« on: March 14, 2006, 01:24:03 am »
Everytime I try to hack my DMS it keeps telling me that I have "incorrect volume labels" also...during the boot sequence it tells me about my keyboard.

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: incorrect volume labels
« Reply #1 on: March 14, 2006, 02:22:59 am »
tells you about your keyboard?  tells you what?  That you have a keyboard?  that a key is stuck?  


Come one why do people post totally random stuff with no specifics about some error they had?

Offline dark_gable21

  • Newbie
  • Posts: 6
  • PhatHacker
Re: incorrect volume labels
« Reply #2 on: March 14, 2006, 02:34:18 am »
Quote
tells you about your keyboard?  tells you what?  That you have a keyboard?  that a key is stuck?  


Come one why do people post totally random stuff with no specifics about some error they had?
what would you like to know?

Offline dark_gable21

  • Newbie
  • Posts: 6
  • PhatHacker
Re: incorrect volume labels
« Reply #3 on: March 14, 2006, 02:38:20 am »
Quote
tells you about your keyboard?  tells you what?  That you have a keyboard?  that a key is stuck?  


Come one why do people post totally random stuff with no specifics about some error they had?
what would you like to know? My point is that in the examples that where given, the text made no mention of a keyboard being attached in any lines of the text.

Offline dark_gable21

  • Newbie
  • Posts: 6
  • PhatHacker
Re: incorrect volume labels
« Reply #4 on: March 14, 2006, 03:35:23 am »
it appears that I needed to repair the dms cartridge.

Offline uplarry

  • Newbie
  • Posts: 4
Re: incorrect volume labels
« Reply #5 on: March 15, 2006, 12:02:16 am »
I had the same problem. Even though the volume labels looked correct when viewed from Windows, they could not be read properly from the DMS software (they were blank). Run the PhatNoice DMS Doctor and repair your DMS. This will fix it.

Offline dark_gable21

  • Newbie
  • Posts: 6
  • PhatHacker
Re: incorrect volume labels
« Reply #6 on: March 15, 2006, 01:14:19 am »
that didn't fix it either.  I had to use the repair utility to get the thing to work. I did copy all the music on to my computer and then repaired it and then updated the firmware. I then stuck it into my musickeg just to make sure it still worked. It did...Then I hacked it. All is well. But, thank you for you reply.

Offline deepthought

  • Newbie
  • Posts: 2
Re: incorrect volume labels
« Reply #7 on: April 08, 2006, 01:30:23 pm »
looks like you're not the only one having this issue. DMS works all right under Windows XP / Media Manager, but I am stuck with the same "incorrect volume label" issue. Maybe the volume can be re-labeled via FDISK or similar? Anyone knows what the correct label should be?
Thanks and good luck to all!
Deepthought

Offline deepthought

  • Newbie
  • Posts: 2
Re: incorrect volume labels
« Reply #8 on: April 08, 2006, 01:43:50 pm »
...and of course I'd be willing to donate 10 bucks to support your valuable efforts!!!

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: incorrect volume labels
« Reply #9 on: April 08, 2006, 09:52:42 pm »
 use the phatnoise DMS repair CD to repair your DMS then reload the firmware from PMM and you should be good... that will set all the volume labels etc

Offline sheriff

  • Newbie
  • Posts: 2
  • PhatHacker
Re: incorrect volume labels
« Reply #10 on: April 13, 2006, 02:24:48 pm »
When usign the dms hack I also have had the incorrect volume labels message appear(volume labels PHTSYS and NO NAME are incorrect........please insert genuine DMS...) this was using an original 10gb dms cartridge which works fine.
I have tryed reloading the firmware and using both the DMS doctor and the repair option on the PMM software - nothing works!!!!! I dont have a repair CD either, as suggested earlier in this post - was this supposed to come with the original package?!
Any suggestions?? as i am about to throw the whole lot out the window as I dont have a clue what to do. PLEASE HELP!!!

Offline sheriff

  • Newbie
  • Posts: 2
  • PhatHacker
Re: incorrect volume labels
« Reply #11 on: April 13, 2006, 03:00:41 pm »
if it helps, the error code i get when using the phathack repair is LBD0004. :'(
i dont really want to contact kenwood customer support, as i am sure they dissapprove of hacking their products!!!!hehe

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301

Offline TommydCat

  • Newbie
  • Posts: 9
Re: incorrect volume labels
« Reply #13 on: April 13, 2006, 11:00:17 pm »
I've noticed on my computer that it seems the runbuild software is trying to grab the volume labels too fast after it detects the cartridge has been inserted.  I get the wrong volume label (nulls) immediately followed by the usb driver reading the correct volume label.

If I run /runbuild again, it now sees the correct volume labels and continues.

Offline jg123

  • Newbie
  • Posts: 14
  • I love my Keg!
Re: incorrect volume labels
« Reply #14 on: April 15, 2006, 02:31:50 am »
Quote
I've noticed on my computer that it seems the runbuild software is trying to grab the volume labels too fast after it detects the cartridge has been inserted.

I noticed that, too. You actually need to insert the DMS cartridge BEFORE you press enter to detect the DMS. Otherwise you'll get those incorrect partition errors if the partitions are good in Windows.
« Last Edit: April 15, 2006, 02:32:50 am by jg123 »

Offline benakiba

  • Newbie
  • Posts: 4
  • PhatHacker
Re: incorrect volume labels
« Reply #15 on: April 30, 2006, 11:28:29 am »
Quote
When usign the dms hack I also have had the incorrect volume labels message appear(volume labels PHTSYS and NO NAME are incorrect........please insert genuine DMS...) this was using an original 10gb dms cartridge which works fine. PLEASE HELP!!!

I have had the same problem. My genuine DMS was set to German language. So, I set all configuration items back to english language and then it worked. Maybe it works for you too...good luck.