News:

I have updated the spam detection on registrations, and as such I am enabling new users.  If we have spam, I will change it back to by approval.

Main Menu

hack disk problem

Started by Anton, May 01, 2006, 04:17:45 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Anton

When I boot from the hack disk, there is no program started.  Runs through system check, caldera Dr DOS, etc... all I get is a command line prompt at A:\  

I dont have a drive assigned A:

Am I missing something basic?

I've tried run command, and changing directories...

judb

I don't know what hack disc you are taking about because the one we built uses Linux and boots into a menu for you to use.  Where did you get that file from?

Anton

It is the CD iso image from your sticky...  :-?

I burned it using Nero.

Sorry, don't know much about linux.

I just made another copy, gonna try again tonight.  I think I messed up the first burn.

timps

Did you use the "burn image" feature of Nero or just copy the downloaded file straight to disc?

Anton

I used the burn image feature of nero
also used the make bootable CD feature.

Both disk give me this when I boot from them:

a bunch of stuff scrolls by...
...



Current options
/MLX               Program is loaded into conventional and xms memory using DPMS
/BL=16            Lookahead buffer is in conventional memory - size is in KB
/Lend=off        Lend memory to other Applications   6646 KB available
/Delay = off     Write delay is disabled,  Caching is write through

Caldera DR-DOS 7.03
Copyright (c) 1976, 1998  Caldera, inc.
[DR-DOS] A:\>

markbowen

You are burning it wrong.

From the New Compilation menu in Nero, click Open, and then select the boot disk ISO (which you should have downloaded from here:  http://downloads.phathack.com/judb/DMS-Hack-or-Repair-v1_5.iso).  This will automatically bring up the Burn Compilation menu.  Just click Burn.

If using Nero Express, choose Image/Project/Copy on the left, and then Disc Image/Saved Project on the right, then click on the same ISO file, then Burn.

Kenwood DNX7200/Kenwood KHD-C710 Keg/320GB DMS

Anton

#6
That, fixed the problem, thanks.

However,  I had a failed message when running the disc.  Failed to copy phtsys to new DMS.

The partition is there, full of files, zero free bytes.
my original phtsys partition had lots of free space.

DMS is recognized by PMM, but will not hold any songs.

What did i do wrong?

This is a VW box, and it does not recognize the DMS.  I tried the genesis method for VW phatboxes.

Anton

The phtsys partition that is created on the Hack DMS is alot smaller than on the original DMS.  by several hundred MB.

I'm Still having problems, and I don't know what I did wrong.

Can I start over?

I never heard the confirmation sound during the box patch.

any help would be greatly appreeiated.

Anton

judb

can you post the test from the logs in the log directory in the phtsys partition?

The size of the partition was reduced because you'll never use that additional space that the original DMS setup used.  The newer phatnoise issued repair disc changed the size of that partition so we just used that logic in our hack scripts.

Anton

#9
After my second run with the boot CD, this:

There is nothing in log directory, but an empty file named logshere.txt

the phtsys partition is full of empty files, 0 bytes, including bootload.log, and box_id_log.txt

Only the phatman.ini, and the Plugins dir, and CurrentSetup.xml have data.


after the first attempt, when I used the genesis method for VW phatboxes, I did have data in the phtsys partition.  I remember looking at the bootload.log, and it listed everything as "succesful"  However, i was still unable to load music.  So I ran the patch disc again.

Using the original DMS in the phatbox is no problem.

Regarding the size of the partition, I was using the extra space to store .wav files for use as random startup sounds.

Anton

#10
judb,

Did you want the log from the original DMS phtsys partition, or the Hack DMS?

Anton

judb

Interesting... I think maybe the firmware on your new DMS isn't installed right.. have you tried reinstalling the firmware?  I'd run a chkdsk on phtsys and then extract a copy of the firmware from unix.phatnoise.com or from downloads.phathacks.com (although downloads was down a few weeks ago and I don't know if it came back up or not)