Print

[cmiz]

hehehe yeah i was just thinking...the last time they gave us fonts, they sorta got slammed

[triggernum5]

It would work with evox, you are just creating the shell of your shadowc in an unconventional manner..  One you fill it up with the proper files it will be just like any other shadowc..

[Olipro]

if they MD5'd it, then it would still be possible to root out a collision for it, so it'd only act as a delay, and for MD5, that shouldn't take an amazingly long time, whereas SHA-1 would really be a pain in the butt.

[Ghengis]

As if this thread wasn't long enough...

Anyway, it doesn't seem to have been updated for release 10, which seems to be current.  I was going to humbly suggest that future releases look to e:\evoxdash.xbe instead of c:\evoxdash.xbe, because that would allow you to make your shadow C drive 100% pristine.  As it stands, evox is loaded AFTER the shadow C is mounted, which means it loads evox from the image, not the actual drive.  Or have I got something wrong here?

[cmiz]

QUOTE(Ghengis @ Mar 4 2005, 03:11 AM)

As if this thread wasn't long enough...

[krayzie]

Well it's supose to write to the actual eeprom. i tested this with the regular configmagic. Altough some weeks ago i changed regions with configmagic 1.6  and it only wrote to the virtual eeprom.

[stoatie_weasel]

Ok, I can confirm that configmagic v1.6 does write to the virtual eeprom and not the actual eeprom.
Didn't feel the need to test the original version of configmagic.

[nprice]

Just to clarify, can I use the driveimageutils 1.0.1 apps with nkpatcher 10? Nkpatcher's readme says:

QUOTE

From version 8.1 to version 9:
 * oz_paulb LBA48 and partition table support

 * Virtual C image may now be of any size. You can make a virtual drive from
   scratch by first creating a file (or copying any old), say 200 MB, and then
   formatting it. You can for example virtualize the F with the unformatted image
   first and then format F using Evox dashboard. Then copy stuff to F and then
   use the done image file to virtualize C. The number at the end of
   VIRTUAL_C_DRIVE option can be used to select any existing drive for
   virtualizing. I'm sure there are also Linux tools for creating a FATX file
   system inside a given file.

I'm not quite understanding this... can someone explain?

[krayzie]

QUOTE(nprice @ Mar 13 2005, 01:31 AM)

Just to clarify, can I use the driveimageutils 1.0.1 apps with nkpatcher 10? Nkpatcher's readme says:

[xman954]

well if 137gig is FFFFFFF (dec 268435455)
and you want 60gig F:\  then set size to 60+8 (8=C:\,E X Y Z)
(68/137)*268435455=133238036 or 0x07f10d14
that should get you close...

[DaddyJ]

QUOTE(dvanbrunt @ Mar 19 2005, 12:46 PM)

I want to know the process so I can convert my 80GB HD F to only be 60GB.

may I ask why?

[dvanbrunt]

Also, if anyone ones what to do with the default.xbe file once created I'm all ears. I have now made compiled the new one but am a bit lost as where to go from here to get it to repartition the drive.

[xman954]

QUOTE(dvanbrunt @ Mar 21 2005, 08:30 PM)

Also, if anyone knows what to do with the default.xbe file once created I'm all ears. I have now made compiled the new one but am a bit lost as where to go from here to get it to repartition the drive.

[dosfan]

From a cold boot? the answer is no:
D:\default.xbe would be executed BEFORE nkpatcher would have a chance to kick in. (I assume you are softmodded, UXE?)

Launching an original disc after nkpatcher would keep the partition hidden, but that doesn't make it safe to XBL.  Kernel memory has still been modified...but you probably already knew that.

[SilentBob1638]

Any plans for next nkpatcher to support mounting Files/IMG/ISOs over SMB share? Would be handy for ppl with stock drives...