yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] mike1986.:
Ok, THX ervius!

Now to succesfully dump os.nb.payload and replace XIP files I have to use "dump" tool in the kitchen, enter device name "DIAMOND" and replace old XIP files with new one and also os.nb.payload, romhdr.bin and xip.bin?
[Windows Mobile] anryl:
kaiser OK 340000 :D
[Windows Mobile] mike1986.:
I dumped os.nb.payload, replaced all files and got error in cooking platformbuilder.exe
[Windows Mobile] ervius:
well :)

try also with -imgstart 360000 and -imgstart 380000 (or 320000)

bye!

@michal_banszel

I don't know the error is from, maybe xip is yet builded with platformrebuilder, or something else, try to dump an original rom and then rebuild it before.....
[Windows Mobile] anryl:
320000 not working as expected

360000 ok works as expected

the best still is on kaiser 340000 :D
[Windows Mobile] bobsbbq:
I'm a little confused, I added the latest implantXIP.exe to the 9.3 kitchen and built a ROM which was working and with the new one it will not boot.
[Windows Mobile] mac_es:
check the imgstart parameter... in kaiser is needed maybe in hd too
[Windows Mobile] CRACING:
Hello ervius,

My another attempt to make visual kitchen, work for my HTC Wizard. Please help.... :o

The only problem is with nbh which it creates at end. I just wanna remove it coz my wizard supports nbf and not nbh. I only want the os.nb to be created and then after I will make it to nbf using nb2nbf tool, manually.

I request again, Please help me.

Thanks & regards
[Windows Mobile] hilaireg:
Hi Ervius,

Trying to support your work; response would be appreciated.

Cheers,
[Windows Mobile] ivanmmj:
Wouldn't it be easier to just create a little bat file that will automatically run the kitchen for you, and when you close the kitchen, automatically delete the nbh file then automatically create the nbf for you?
[Windows Mobile] Da_G:
Hi ervius, guess u missed my post where I had already tried 20000 less (760000)

tried it again with new implantxip, no boot as expected.

20000 higher (800000) works fine as you would expect.
[Windows Mobile] CRACING:
Ok, I made the same thing but after flashing the ROM. I'm getting my old ROM, mean the ROM isn't flashing.

WinMo 6.5 is the working ROM in my device; I flashed the cooked ROM ( from visual kitchen ) ( WinMo 6.1 ); says successfully flashed in ruu but still I get WinMo 6.5 which is my previous flashed ROM. :(

BTW; I tried to extract the cooked nbh and then recreated to nbf ( as you said ). Also tried OS-new.nb from temp but same problem.

Edit 1: Ok I found it. It should be ..\TOOLS\IMGFS\ImgfsToNb imgfs-new.bin OS.nb.payload OS-new.nb -conveservative. Now flashing. Hope it works :)

Edit 2: YES I GOT IT. Its working prefect now. BOOTING = OK, XIP = OK; SYS = OK; ROM = OK. :D

Thanks & Regards
[Windows Mobile] mike1986.:
with new implantxip.exe my ROM cooked succesfully but don't boot...
[Windows Mobile] ervius:
only have to modify the "kitchen_build_rom.bat" at your needed, instead to run "nbhutils.exe" you can run other tool and create the nbf file instead ;)

@hilaireg

you donated to bepe, and only to him, but I'm happy, becouse he created the base kitchen £platformrebuilder", without all visualkitchen cannot exists ;)

bye!!!
[Windows Mobile] ervius:
ok, version 9.5 of visualkitchen in few minutes will be ready at 1st post 8some other bugs solved from "font size set" if an error appear during 1st load of visualkitchen!) and more:

new version of implantxip.exe:

if -imgstart is omitted, it read the imgstart from Payload into MBR Section, and set minimum IMG start value the value found into payload, so, if the xip.bin is shorter, it remain same value for IMG section start, if xip.bin is greater, it moves imgfs section until it have free space to insert new, bigger xip.bin into payload ;)

bye!!!
[Windows Mobile] CRACING:
Yeah, I'm made the samething and got it working. I think I tried the samething long back ( May be within v3 to v5 ) and it wasn't worked or I was wrong that time. However its working prefect now. At present I have mine kitchen which is based on platform rebuild and its of dos and very simple. And now a new kitchen thats yours ( GUI and very powerfull ).

Thanks a lot.
[Windows Mobile] mike1986.:
I hope my diamond will boot now :)
[Windows Mobile] sleurhut:
Translation and not working Start Menu

If you create another language ROM you must use in de Base_Lang... folder

use the translated shellresapps.dll.04xx.mui and shellres.dll.04xx.mui modules. It solved the not working StartMenu ;-)

This worked in this kitchen.

Now i must see how i get our other components in it :D
[Windows Mobile] mike1986.:
My Diamond finally boot correctly D
[Windows Mobile] Da_G:
hi ervius, correct me if i'm wrong;

does xipporterex not correctly resize xip partition to be smaller than original without causing no boot problem using "rom tools"?

perhaps this logic could be applied to implantxip?
[Windows Mobile] utak3r:
DOS?... I don't think so :p
[Windows Mobile] CRACING:
Yes, dos based. Ah sorry, I don't know the exact word but it looks like dos ( The platform rebuild ).
[Windows Mobile] utak3r:
It's a Windows' console, not a DOS :p

I wouldn't say that, but I grewed up in DOS, so... :D
[Windows Mobile] anryl:
question

how are sorted EXT packages ? not by name not by date by what ?

i need to make EXT by name sorted how to proceed ? :cool:
[Windows Mobile] CRACING:
OK but both looks same and may be command lines too :)
[Windows Mobile] ervius:
sort them:

device packages:A-G

device common:H-M

sharedpackages:N-Z

maybe this must be the good sequence....

report then.....
[Windows Mobile] anryl:
i dont get it i need it sorted

PACKAGE_A_ELFIN

PACKAGE_A_IOLITE

PACKAGE_A_JADE

PACKAGE_A_KAISER

PACKAGE_A_OPAL

PACKAGE_B_ELFIN

PACKAGE_B_IOLITE

PACKAGE_B_JADE

PACKAGE_B_KAISER

PACKAGE_B_OPAL

PACKAGE_C_ELFIN

PACKAGE_C_IOLITE

PACKAGE_C_JADE

PACKAGE_C_KAISER

PACKAGE_C_OPAL

but its not working

EDIT: solution COPY ALL PACKAGES INTO DIR SORT BY NAME IN TTCOMMANDER THEN COPY WITH THE SORT ORDER TO NEW FOLDER THEN ITS WORKING
[Windows Mobile] dioooi:
Dear Ervius

Very good tools, do you have any tutorial note to teach how to use it?

Thanks
[Windows Mobile] hilaireg:
Take 2: Donation

Fair enough ... let's try it again; this time I clicked the PayPal button in Kitchen 9.3.

Transaction ID: 3D631667R30117324

Email: upsetbrain@hotmail.com

A confirmation of receipt would be appreciated.

Cheers,
[Windows Mobile] NRGZ28:
Hi erv.

Suggestion for EXT packages folder structure please :)

Right now, I can one subfolder in "SHARED" and package folder right under it. But if I create another subfolder, the kitchen doesnt see the packages anymore. Do you think it's possible to modify your kitchen to see more than one subfolder deep ?

Something like... EXT\SHARED\PPC Packages\My Packages\Adobe_Reader_1212121\

Right now I can only do EXT\SHARED\My Packages\Adobe_Reader_2232323\

:)

One more thing... think we can get a folder in \EXT somewhere... that can be hidden from view in the main kitchen interface ? That way I can put all the packages that never need changing in that folder and I never have to scroll past them in the kitchen. You know something like.. \EXT\SHARED\ALWAYS INCLUDED\ or EXT\DEVICE\ALWAYS INCLUDED but never shown! :)

Or even better... maybe create an algorithm in your kitchen to look for "HIDDEN" or "DONTSHOW" in the folder name and when it detects that, make it not display in the main kitchen UI ? :) That would be awesome.

If you could make that happen and my first suggestion to be able to have deeper folder structures... I promise another 20 euros from me :)
[Windows Mobile] ervius:
for now I have other to think.....

In MBR analyzing.....

I found something interesting, and maybe the causes of non-booting for rom payload (maybe original and not fixed by my Xipporterex!)

work on it, my friends, I don't have many times to experiment all described ;)

bye!
[Windows Mobile] uhery:
Hi Anryl,

had the same problem ... only an idea & just a question ... which OS do you using?

because i tried "vista" and i think i remember the packages were on alphabetic order ... (but, now, i can not try on it)

so ... in this moment i am working only on xp ... and the order seems .... "random" ! :D

or better seems ... the time that you made the sub-foder packages inside the main folder ...

would you test it? :)

1. move your packages ( PACKAGE_A_ELFIN PACKAGE_A_IOLITE etc .... ) out of the kitchen

2. put back in an empty-main folder (i.e. folder "build") your packages but using the order that you like ...

that's all! 4 me works! :)
[Windows Mobile] ervius:
all this theory was correct, I reduced xip-size (untouchable until now, or the rom didn't boot before....)

and used to reduce uldr partition, and now rom boots ;)

some and I'll post it and a complete comman dline witt optional commands ;)

bye!
[Windows Mobile] ervius:
new version of implant xip:

all commands here: ("["are optionals"]")

implantxip -xip xip.bin -payload OS.nb.payload -imgstart 340000 -uldr

(implantxip -xip xip.bin -payload OS.nb.payload [-imgstart 340000] [-uldr])

"-uldr" means that it reduces uldr part if not yet reduced!

bye!
[Windows Mobile] ivanmmj:
Using this implantxip, with or without the -uldr, closes before doing anything.
[Windows Mobile] ervius:
I tryed on diamond, maybe have to see your payload, post it to me in pm....

P.S.: I tryed with -imgstart 320000 and works fine now,waw!!!, maybe all bytes needed to be realligned..... ;)

01 00 20 3F 01 00 02 00 00 00 3E 00 00 00 00 00

01 01 23 3F 01 18 40 00 00 00 00 06 00 00 00 00

01 19 25 3F 81 D0 40 06 00 00 00 AE 00 00 00 00

81 D1 04 3F 81 98 40 B4 00 00 00 F2 00 00 55 AA

this is my actual "MBR", see the XIP lenght! ;)
[Windows Mobile] anryl:
tested kaiser ..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -uldr

booting fine
[Windows Mobile] ervius:
well, you had all that I need to complete tests, no "FAT" section on payload and rom allignment to 0x10000 and not to 0x20000, well, seems to works now.....

try this last version of implantxip ;)

bye!!!

P.S.: if yet downloaded, try this other ones ;)

bye!
[Windows Mobile] ivanmmj:
Did I ever tell you how much you rock? haha You Rock!!
[Windows Mobile] ervius:
yes, but retry with the second one posted, also xip allignment is 0x10000 and not 0x20000, refixed for U ;)

bye!
[Windows Mobile] ivanmmj:
The first one booted but didn't really remove the ULDR, the second one I'm trying right now. I'll report when I finish.
[Windows Mobile] ivanmmj:
It's not shrinking it. hmm...

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00010000

ROM Block is : 00000200
NO ImgStart....
From IMG Value: 00620000
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target: size :0030FFFF
ULRD in Payload Start:00000400 Size:0030FBFF End:0030FFFF
XIP in Payload Start:00310000 Size:0030FFFF End:0061FFFF
IMG in Payload Start:00620000 Size:0000FFFF End:0062FFFF
FAT in Payload Start:00000000 Size:00000000 End:00000000
After:
XIP.BIN Target: size :0030FFFF
ULRD in Payload Start:00000400 Size:0000FBFF End:0000FFFF
XIP in Payload Start:00010000 Size:0060FFFF End:0061FFFF
IMG in Payload Start:00620000 Size:0000FFFF End:0062FFFF
FAT in Payload Start:00000000 Size:00000000 End:00000000

Payload resized and XIP Inserted into: OS.nb.payload
[Windows Mobile] ivanmmj:
I'm a little confused about the imgstart. Right now I'm just using:

..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -uldr

The phone boots just fine but the ULDR isn't being taken off (like stated above.)

I don't understand where the imgstart value comes from and if it's even needed.

EDIT: Strange... If I try to manually remove the ULDR, then run the command, it DOES move it from 0x20000 (where I placed it) to 0x10000.

EDIT2:

Stranger and stranger....

I tried it again and I got this:

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00010000

ROM Block is : 00000200
NO ImgStart....
From IMG Value: 00620000
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target: size :0030FFFF
ULRD in Payload Start:00000400 Size:0030FBFF End:0030FFFF
XIP in Payload Start:00310000 Size:0030FFFF End:0061FFFF
IMG in Payload Start:00620000 Size:0000FFFF End:0062FFFF
FAT in Payload Start:00000000 Size:00000000 End:00000000
After:
XIP.BIN Target: size :0030FFFF
ULRD in Payload Start:00000400 Size:0000FBFF End:0000FFFF
XIP in Payload Start:00010000 Size:0060FFFF End:0061FFFF
IMG in Payload Start:00620000 Size:0000FFFF End:0062FFFF
FAT in Payload Start:00000000 Size:00000000 End:00000000

Payload resized and XIP Inserted into: OS.nb.payload

Yet the payload file didn't change in size. Is it not supposed to change in size? (It does when I remove the ULDR manually.)
[Windows Mobile] ervius:
I have to play some with it, in conventional payload all works well, but I can check, on yours, I have to see better what to do!!!
[Windows Mobile] ervius:
I tryed and works well....

************************

NO ImgStart....

From IMG Value: 00620000

************************

you didn't write the minimum IMG start value, so it find 0x620000 and resize xip part to have img start at 620000, try this command:

implantxip.exe -xip xip.bin -payload os.nb.payload -imgstart 320000 -uldr

and you'll see that os.nb.payload from 6.5 Mb, became arond 3 Mb, exactly 3.2 Mb ;)

and see what appen:

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00010000

ROM Block is : 00000200

IMG Min Value : 00320000 ULDR Reducing...
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target: size :0030FFFF
ULRD in Payload Start:00000400 Size:0030FBFF End:0030FFFF
XIP in Payload Start:00310000 Size:0030FFFF End:0061FFFF
IMG in Payload Start:00620000 Size:0000FFFF End:0062FFFF
FAT in Payload Start:00000000 Size:00000000 End:00000000
After:
XIP.BIN Target: size :0030FFFF
ULRD in Payload Start:00000400 Size:0000FBFF End:0000FFFF
XIP in Payload Start:00010000 Size:0030FFFF End:0031FFFF
IMG in Payload Start:00320000 Size:0000FFFF End:0032FFFF
FAT in Payload Start:00000000 Size:00000000 End:00000000

Payload resized and XIP Inserted into: os.nb.payload

bye!!!
[Windows Mobile] ivanmmj:
That worked beautifully!
[Windows Mobile] ervius:
well, and at 1st post "implantxip_final.zip", it can work with all kind of payload file, and more:

if a payload has ULDR removed (ULDR part not present!), it can work on it and reallign well some bytes into MBR ;)

bye!!!

P.S.: the uldr removal have to be done by hands!!!

only to make compatible implantxip with all kind of payload, original, fixed, reduced and "cutted!

bye!!!
[Windows Mobile] ervius:
another new version of implantxip, now after -uldr you can write (optional) "tryremove" (without quotes), to try to remove completelly the ULDR Part on MBR and Payload. NB: I don't know if this option is good for all kind of payload files!

bye!
[Windows Mobile] Ameet:
I dont think removing the ULDR completely is possible since it may screw up the requried sector size calculations :) Like in Diamonds, at the most we can have it reduced by 3 mb :D
[Windows Mobile] ervius:
yes, but backupping the original payload file, and trying to do it costs some time more and we can understand if is possible for all roms ;)

P.S.: now implantxip calculates all size of all sectors (ULDR,XIP,IMG,FAT) and replace completelly the MBR part ;)

bye!!!
[Windows Mobile] ervius:
I checked on s000 of nk.exe and seems that all work well on....

maybe have to check better.....

try this patched nk.exe.....
[Windows Mobile] RideTheTube:
will try it now - thank you very much!

EDIT:/ Still the same - it will not boot...hmm i dont know..
[Windows Mobile] ervius:
maybe is something else, try without patch the cert on....
[Windows Mobile] RideTheTube:
what a bummer ,it still no works for me. if i cook in an other kitchen it works.

maybe there is a vista x64 problem? I will try it in Vmware and give you feedback.

thx ervius
[Windows Mobile] furb3t:
First of all, Ervius thanks for sharing your visualkitchen :)

Now let's come to problems :)

1. If I setting ROM VERSION, rom isn't created. I have to left 2.0.00.0 to create kaiser Rom.

2. I compared 2 nbh, one from traditional kitchen and one from visualkitchen, and I saw that the dimension of rom created by traditional is more bigger than the rom created by visualkitchen. For ex:

Rom by traditional = 95.554 MB

Rom by visual = 55.675 MB

What's this difference?!?
[Windows Mobile] ervius:
maybe you leave some steps, I don't know.

if you don't respect the structures, for example:

into a package you have only 04xx with into some files, and not 04xx\files, with insode some files, platformrebuilder doesn't copy them into \dump folder. (I don't know if is a bug, but is what appen!)
[Windows Mobile] ervius:
I've just dumped this rom:

RUU_Kaiser_HTC_ITA_3.29.408.0_radio_sign_25.83.40.02_1.65.17.56_Ship.exe

and os.nb.payload is 92 Mb, after build new with visualkitchen, new os.nb.payload is 72 Mb, but comparing both dump\ folder with "beyond compare", I have:

1) original dump\

2) remaked dump\

1) 1758 files

2) 1758 files

so, no files or modules were lost, only in modules, like platformrebuilder.exe uses, all last S00X are lost (is a new bepep protection!)

so no problem if you have a payload smaller tghan original, you have to enjoy, same files/modules, more and more free spaces into device ;)

bye!!!

P.S.: same with hermes rom:

ROM HTC TyTN Ita 3.54.258.2_102_6275_1.47.00.10_108.rar

compared both dump\ folder same files/modules number..... different total space into old/new payloads....

more free space!!!!!!
[Windows Mobile] furb3t:
Ok...i'll try to flash this new Rom cooked by your visualkitchen and I'll report you :)

For ROM VERSION problem !? Any idea?
[Windows Mobile] ervius:
yes, but remember to modify os.txt and build_rom.bat, according with your device ;)

I don't know what you mean, version on first boot, or in info device????
[Windows Mobile] furb3t:
I mean the Input Box labelled ROM VERSION in your visualkitchen (in the right top).

I see os.txt but what does it mean in " 400,..\temp\OS-new.nb" the number 400?!

Then in build_rom.bat in which part have I to modify in according with my device kaiser?!
[Windows Mobile] ervius:
nothing, for kaiser nothing into bat file,

the "400" means the offset where write the os.nb into nbh file! (and usually is same for all devices!)

into os.txt

diam****

with

kais****

and HTC__001

with

11111111

bye!
[Windows Mobile] ibrythill:
I've got a little error. When dumping a rom with "dump nbh/nb/payload" and trying to cook a ROM I got an error: Error Executing: kitchen_build_rom.bat.

Everything is ok when I use Nb_Dumper.exe. Any ideas?

EDIT: Found what was cousing the error. I had second rgu and forgot about it. Perhaps the kitchen should have a tool to tell you wat's wrong and where?
[Windows Mobile] RideTheTube:
Hi back again^^

i have tried it in xp now but no glory...:(:D

just to test i dumped a working Diamond Rom from me but if i dump it with visual kitchen and change nothing just click on Create Rom (left upper) does not boot?

Should i make some screens from my folder structure?
[Windows Mobile] NisseDILLIGAF:
Nevermind... I figured it out...

I forgot to put the EXT_Pakages in a folder under EXT... :rolleyes:

Hi...

I have a problem when building the nbh file...

I think It's something with the folder structure...?

There are files missing after I flashed the ROM

My folders look like this...

Is this correct, because all files in the (common) folder 'files' don't get included in the build...
[Windows Mobile] ervius:
see the structures of my visualkitchen posted at 1st post.
[Windows Mobile] ibrythill:
Is it possible to make a "unprotected" ROM with your kitchen? And perhaps how to do it?;)
[Windows Mobile] ervius:
no, with bepe's platformrebuilder.exe you cannot.

P.S.:

erviuskitchen only exe prerelease rom prj saver version ***6***

at first post!

added:

all modules and files automatic analyzer before build rom, to prevent that a file overwrite a module, if same name, that causes Bepe "platformrebuilder.exe" crashes on rom build.

if some files and modules are present with same name, rom cannot build, you have to delete all duplicate files from modules, and finally you can build yur rom.

bye!!!
[Windows Mobile] ervius:
seems that bepe's platformrebuilder has a little bug:

if:

a module overwrites a file: noting appens and platformrebuilder works well...

a file overwrites a file: "Warning", but platformrebuilder works well...

a file overwrites a module:"Warning", but platformrebuilder crashes...

a module overwrites a module:"warning", but platformrebuilder crashes...

ok, I'll update visualkitchen, so it will check if a file or a module wants overwrite a module!!!!!

revision 7, check on file to module overwritting / module to module overwritting.....

download at 1st post!!!

bye!!!
[Windows Mobile] spocky12:
Thanks Ervius, your tool gets better and better with each version.

I've notices a small bug with latest revision : it checks for duplicates even for files explicitely flagged as "do not include".

Do you know the order of rom build for ext/sys/oem forders ? I've got some oem\*.rgu files that should overwrite a few values from other rgu and that's not the case, it seems that default.hv and user.hv are not the same than with good old PkgToolsBuildos-4.3b1, is the order different than before ?
[Windows Mobile] ervius:
yes, you are true, try revision 8 (at 1st post!) ;)
[Windows Mobile] bobsbbq:
I'm trying to understand the implantxip.exe function. I know it is called from the kitchen in the .bat file but to run it manually do we run from command prompt and what are the correct parameters to remove the uldr. Do you have to have brackets etc. etc. Where do you get these values from?
[Windows Mobile] ervius:
use it write "implantxip /h" (without quotes) to see all options,use tryremove parameter, and if rom boots all is ok, if not, use only -uldr option.

I tryed uldr remover on Diamond, and does'n start, with only ULDR reducer, all works ok ;)

bye!
[Windows Mobile] mike1986.:
What exackly gives uldr reducer? Is it worth?
[Windows Mobile] ervius:
search on this forum.....

P.S.: version 9.6 at first post.

inserted last implantxip, and solved 1 bug on oldstyle Package importer ;)

bye!
[Windows Mobile] mac_es:
Whith a cutted ULDR xipporterex crashes...

Also one question:

this is what it shows:

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00020000

ROM Block is : 00000200

ImgStart MIN Val. SETTED - ULDR REMOVING...
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target: size :0027FFFF
ULRD in Payload Start:00000400 Size:0001FBFF End:0001FFFF
XIP in Payload Start:00020000 Size:0027FFFF End:0029FFFF
IMG in Payload Start:002A0000 Size:0001FFFF End:002BFFFF
FAT in Payload Start:002C0000 Size:0F7BFFFF End:0FA7FFFF
After:
XIP.BIN Target: size :0027FFFF
ULRD in Payload Start:00000000 Size:00000000 End:00000000
XIP in Payload Start:00000400 Size:0029FBFF End:0029FFFF
IMG in Payload Start:002A0000 Size:0001FFFF End:002BFFFF
FAT in Payload Start:002C0000 Size:0F7BFFFF End:0FA7FFFF

Payload resized and XIP Inserted into: os.nb.payload

I shouldn't look like this?:

After:
XIP.BIN Target: size :0027FFFF
ULRD in Payload Start:00000000 Size:00000000 End:00000000
XIP in Payload Start:00000400 [color="red"]Size:0027FFFF End:0028FFFF[/color]
IMG in Payload [color="red"]Start:00290000[/color] Size:0001FFFF [color="red"]End:002AFFFF[/color]
FAT in Payload [color="red"]Start:002B0000[/color] Size:0F7BFFFF [color="red"]End:0FA6FFFF[/color]

cheers
[Windows Mobile] bobsbbq:
Where are these reports with this data coming from? Is there a txt file generated or is this a print screen from the DOS window? I still can't get the implantxip to work. Tried it yesterday and my os.nb.payload size went up in size.