Print

[JaXbox]

Sweet release devz3ro - works perfectly here..

[joop]

Anyone having ideas why unleashx doesn't work correctly on a virtualized drive?

[rmenhal]

QUOTE(joop @ Jan 11 2005, 08:50 AM)

Anyone having ideas why unleashx doesn't work correctly on a virtualized drive?

In what way? I've used it there and it was fine.

[joop]

If I use nkpatcher10 the following situation:

%define DASHBOARD_PATH '\Device\Harddisk0\Partition7\evoxdash.xbe'
%define VIRTUAL_C_DRIVE 2
%define ACTUAL_C_DRIVE 7
%define VIRTUAL_C_PATH '\Device\Harddisk0\Partition7\shadowc.img'
%define VIRTUAL_EEPROM
%define VIRTUAL_EEPROM_PATH '\Device\Harddisk0\Partition7\eeprom.bin'

In the not-virtualized situation disk look like:
C:\fonts\bert-generic.xtf
C:\fonts\ernie.xtf (points at C:\default.xbe)
C:\Skins\ (unleashX skins)
C:\Config.xml (unleashX config)
C:\default.xbe (nkpatcher build with the aformentioned options)
C:\eeprom.bin (made with evox)
C:\evoxdash.xbe (unleashX)
C:\shadowc.img (empty file created; formatted and filled with newest msdash)

What happens is that the config.xml is not used by unleashx. Looks as if it can't find it. Settings won't be saved. This has been posted earlier in this thread too...

[Kyro]

QUOTE(rmenhal @ Jan 11 2005, 09:32 AM)

In what way? I've used it there and it was fine.

[rmenhal]

QUOTE(joop @ Jan 11 2005, 10:30 AM)

If I use nkpatcher10 the following situation:

[joop]

QUOTE(rmenhal @ Jan 11 2005, 10:37 AM)

Does UnleashX have G drive enabled by default? If it doesn't then obviously it can't use config or any other files on the G drive.

[rmenhal]

QUOTE(joop @ Jan 11 2005, 11:51 AM)

Funny thing is that evox requires enabling too, but doesn't mind running from a virtualized environment...

Having your real C drive as a G drive isn't "virtualizing" and is technically separate from the virtual C drive feature. You could have your C drive appear as G drive by just setting up such a partition table. Actually that's what nkpatcher does with ACTUAL_C_DRIVE setting. It just uses the partition information for Partition2 for Partition7 (or whatever the partition numbers you use in config.inc are.)

I tested the setup with UnleashX in Partition7 and when the dash boots it always overwrites G:\config.xml with a default config. You can change the settings and the modification are written to disk. But when you reboot UnleashX doesn't read them, just overwrites the file with default. If you use Partition6 instead, then it works fine. So I guess this is an UnleashX bug, probably something to do with it not having Partition7 "enabled" early enough when initializing itself.

QUOTE

Would it be possible to virtualize the bios? If so...., well I guess not, but you would be able to go live???

MS could detect this kind of virtualizing stuff by implementing specific tests for it.

[joop]

QUOTE(rmenhal @ Jan 11 2005, 09:11 PM)

So I guess this is an UnleashX bug, probably something to do with it not having Partition7 "enabled" early enough when initializing itself.

[rmenhal]

QUOTE(joop @ Jan 12 2005, 09:17 AM)

Sounds reasonable, BUT... then they would have problems with this if installed on a real G-drive too, woulndn't they? And the same for a real F drive too, which is not the case.

Yes. There's no problem when having ACTUAL_C_DRIVE 6 here either.

[almirf]

Friend Rmenhal and Friends of Forum !!!

[PedrosPad]

QUOTE(almirf @ Jan 12 2005, 01:20 PM)

Friend Rmenhal and Friends of Forum !!!

[anjilslaire]

Funny issue:
I've got nkpatcher all set up on mybox via UXE Complete .02, tweaked for shadow c: (retail), and unleashX on F:. Everything boots fine. However:

Everyone raves about how much faster nkpatcher is than pbl. Not in my case. I get a fade in effect like the older pbl's from the retail "X". It actually takes a few seconds (haven't timed it), but is longer than PBL metoo was definately. I didn't change anything in the config.inc file except partition locations, dash location, etc. Is it slower because it's mounting the shadow C ?

It something I can easily live with, but it's definately not faster like I've heard.  Any suggestions? Running a 40gig 5400rpm WD drive.

[total_ass]

hmm less than a second after the ms logo appears my dash has loaded, this is with a moved c partition and image drive.

[total_ass]

yeah i think (but not certain) that the ms logo indicates when it has started loading from the hard drive, after checking for a retail disc and after the flubber.