-I-

Yet another update last weekend i recieved an email from ntcore, with the private link to a first version of the patcher. sadly enouth my own harddisk on my x64 workstation is dying on me and though its still in warrenty and i also have a spare disk arround, I have yet to find some time, to swap disks and call in for warrenty... xpero already has HIS version so im confident it'l work out, also at this point im rather unsure about what will be the course for: xp64 (should it it be a backport of: vize or a clone to: xpize... ) i hope xpero can shead some light on it...

Quit update

the language use for your aplication doesn't realy matter that mutch i think because the patches themselves are probably done by reshacker anyway, so the only 'programming' you will have to do is > creating a nice control pannel thingy to enable or disable some of your feature... > a tool to scan your patched files (to check for changes and updates) to see if you need re-patching them > an install & uninstall process the the rest is done by reshacker anyways... specailly if this is something you do because you want to learn stuf from it.... i would recomand you to use Microsoft's native MSI installer i think there are alrealy quite some good code examples in .NET for you to see how other people have done this.. and ill try to monitor your project if xpize64 wil let me. wishing you mutch luck

it really depends on what you are looking for, but any ( 32bit supporting) version of vb / delphi or other language will do, even batch files would work perfectly but like i said before, the old reshack.exe will make your life mutch easier.... its known, there are lots of example's in current xpize versions (to show you reshack scripts) ... and you can start right away... the new patcher for you will be probably slower (at least at first), will take some time to debug etc. specially since there is no 64bit version of win2k - it serves absolutely no use for you,

well that depends on what other aplications youl be using on your win2k box, example i used to have paint.NET installed - but when paint.net went away from 2k and nobody really filled the gap (backporting new features to win2k), i droped it from my install and replace it with another app most other apps i use dont even use .net 1.1 so i might even consider dropping net.20 in full for any box i manage. thats why i really dont understand why the move to a 64bit patcher (that most likely will be a bit slower) - for an old os like win2k its really useless to even cosider it... you might ask me why im telling people to move to a potentialy slower patcher for xp32 than, yet that is JUST and ONLY JUST because developing 1 single base for all xp and vista versions will be mutch easier than managing 2 seperate versions, if i was to be building a 2k version id be sticking it with reshacker and probably something as simple as a compile batch script, something coded in VB.4 or resembling ...

mimicing windows 9x is the most useless idea i ever found to be in existance. here is why... winDOS is a single treaded kernel that is verry outdated.... is ui isn't more usefull than any other guy.. its aplications are outdates by opensource linux aps... to keep it really simple... if your thinkin of even using windows 9x - try linux first. for an example try something slacky, with openbox or fluxbox or if your hardware supports it even xfce ... if you want to play your old dos games there is dosbox if you want to play win95 kind of game first search google name-of-yourgame + linux or install wine .... all other apps have long been developed for linux native and support newer features - even on your old p1 p2 p3

in short: for now this patcher will most likely only aply to new projets, even though in theory it will possibly allow for combined versions of 32- and 64bit editions. (as this patcher support both). in real practice you probably dont want to do all the extra work when rshacker.exe can do the same thing, its not intended to this topic but to answer your and other peoples questions... for older versions of 32bit windows you probably have a choice between this and the old xpize versions... though its not verry likely that you want to port your packs to this patcher on win2k as it most likely will only cost you a lot of time .

this space is reserved for aditional information, or updates

Dear XPize and Vize Users. Maybe you have wondered about why there still isn't any 64bit version of either xpize or vise, Wel let me start by telling you that we did not forget you, and we did not just ignored you. The reason why up till today there no version for you is that we simply do not have the tools and resource to build it for you.. huh? In contrary to other projects xpize uses live updates of the pictures inside windows, The advantage of this method is very important because it will let you be able to run windows update, (witch replaces your patched files so after than just patch the new files again) so you can have your system up to date, protecting you agains the latest bugs and hacks.... The downside however to this is that up until now there was simply no program availible that could do this patching on windows x64 bit files. Thus in the time between xpize first came to be stable, and now, we probably got over 100 requests for a version that we simply had no way of creating. The good news Things are chaging and lots of people including me have start a search for somebody who who could help us out. and thanx to Icy EyeG: (formarly known as 'volvox') who actual made first contact there is now somone from NTcore modifying his resource patcher to support all the commands and scripting that we need to creat xpize64 and vize64 At this point i am prommised a testversion of the new patcher within 1 month from now, so you will probably have to be patiant a little while longer. So what is going to happen now? Well first we all have to wait for the verry first pre-alpha (probably not so stable) test version of the scripting interface of the patcher. as soon as we have it we probably wil need to test what it can do, and give feedback to the developer. when the patcher gets anywhere near stable, we will have to slit up into 3 ways.create test packs for xp64 and vista64 create documentation about how things work diferently from what resource pack authors were familiar to. continue to help ntcore improve both usabillity and stabillity of the new features [*]than after some time people will be invited to start testing the first beta's in live action however its verry uncertain whether this will be within weeks or months from now.. [*]whatever happens after for now is stil verry mutch in the dark and there is now way of predicting any kind of timescale. we all just have to be verry patient, and verry supportive. So what can I do to help Well i have asked ntcore to open up a paypall account and i think that for his effords and really helpfull possition towards me and others, and i really hope thant once i can post his details in here you will be as generous as you have been with other msfn projects and support him and us in improving stuf even further.. Conclusions by now you guys should know that we are committed to doing this as fast as we can, and the more time we spend on replying on questions like "is it really comming soon" the less time we have to actually work on it... // this topic should be sticky'd //

yet another update yesterday i posted the comment about the paypall thingy, and also added that he schould contact me if he want live feedback or any testing today he asked me if he could have my contact-info to be able to send a verry early test version as such i suspect that ill be getting some kind of alpha version soon, at this point i susspect that is wise to start organizing a kind of development team for ?ize64 as is done with the vize project plz note that im not the guy to chose team members based one who asks first or who offers the most money or even can give me the best blow# (nevermind) it probably will be a search in this forum, for those who participated the most, seam to have the best knowlegde who will be than asked IF they have an x64 supporting machine and are willing to help out. and even then it WILL be up to expero to deside

Sure ill do that, but in the meen time tell me how to setup up a paypall account of my own, else i wont be able to donate myself

Update, - hes working on it, - even though i have yet to recieve any kind of test version, im verry confident that the new features will be availible for testing soon, as was to be expected: the patcher will support mutch more than just adding or changing bitmaps, - this would enable you to remove uitdated crap .... unused (bloated) resources and / or probably apply patches (like the raid hack, or thee tcpip patch), also the patcher is going to be getting 2 seperate ways of control. a command line like : patcher.exe /update whatever.bmp blaat something. and a resource script: like something sumular to..... openfile[filename.dll] addresource = res1.bmp addresource = res2.bmp savefile[filename.dll] also with a lua-scripting-interface inside the patcher itself, we may even be able to import settings from a config file or menu interface (suspecting), as im not yet sure about the used IDE the advantage of this would be that [*] anyone can create addons [*] updates could be applied per file (or fileset),

will try..... thnx...

i have a legit version of vista home premium (came with my laptop), witch didn't come with an install dvd, but i figured the license key is on my machine so no real problem to get a dvd iso from the net and use that... my question is, i dont own ultimate n'or buissness, so ill never install them, but i would like to be able to have a disk with just a super-small home basic and a slightly larger home premium both on one disk... now ive noticed that you can rip the disk and create an iso as if it where just 1 version, but would it also be possible to at some point 'remerge' 2 of those iso back together again - and if so???? how

so you disregarded his answer and went away anyways... though i think that his 'no' could have been a bit more explaining, he still was right, so now your stuck with xplite witch is a total piece of crap, now let me get you ONE advice, Take a virgin xp cdrom, re-slipstream all the packs you DO need (be sure that your not installing any you dont want or need)... and re-create your cdrom .... now go Re-install XP the 'right' way, cuz, its a waste of time trying to fix, or debug your current system...

This will probably be atempted, but no garantee s though, as the new scripting method will be 'slightly' diferent from the old. Lets just wait and see, the used component for the scripting engine is realy fast, and also quite exensive, but i have no idea how the PE-explorer will perform as there is simple no real way to test befor its ready, on the other hand, 1 patcher for all; XP, XP64, Vista, and Vista64, will benefit verry mutch in terms of maintainance in your code, so even IF it wasn't faster than reshacker, the deployebillity will probably benefit enought anyways... specially after the next full version of his suit, with would have a small stand-alone patcher that is way smaller than the full suite... so that will help a verry lot...

Work in Progress... just wait and see but i have just one question, as Ntcore is implementing the 64bit patcher ther is one new problem, what / how are the windows patchers like Windows File Protection, and Uxtheme .dll done and what is neaded for it... because if any aditional features on the patcher are need for that... i guess NOW is the time to ask... as well all know that we dont want to get stuck with an old version thats manually patched...

quote from ntcore's blogg: once the patcher is ready its up to the xpize packagers to start working on the *batch * scripts to replace the resources in xp64 ... however, if xpero desides to include this patcher as the new default one for XPize (?NG?) wich i hope, it might take some extra time, but it WILL certainly be worth the wait....

doomangel, i guess you probably did not read this entire topic, so i wil sumarize if for you, Xpize has been there for a long time now, and since became open source (hense all the other shellpacks like darkside), now where are comming at a point where it neads to be ported to vista, (probably be ported to a better resource editor (for vista icons) and mutch more), yet since xpize no longer works really well, xpero desided to build a new app from scratch .... im sure once this app is anyway near usable for the general publik hell release it, and im verry sure it will support other themes, or icon set just as xpize...

posting guidelines: "add you settings. -file if you post any questions here.... " (* Note to forum admin ) [feature request : about "the terms of service" /] [ADD] "by joining and/or posting on this forum, i declaire that i have read and understand, that i must allways first read the posting guidelines on any (sub)-forums before i participate in any conversation in them" [/ADD]

here is how: take an xp sp2 cdrom (pref the one you had used before, or one with the same settings (execpt for the unattended part), dont intergrate any drivers ..... use driverpacks.net 's tool to intergrate AT LEAST the mass strorrage pack (selecting the option for textmode.sif intergration).... go about as you did before (cuze now you have a cdrom than includes a few more sata and scsi drivers to work with...

i just hope that both 32bit AND 64bit versions with include the same patcher so all versions will work the same way...

include error message - and settings file

@ LordWarlock: i first posted it that way too: [FILENAMES] Exe=ExeFile SaveAs=SaveAsFile Log=LogFile [COMMANDS] -add ResourceFile, [ResType],[ResName],[ResLang] -addskip ResourceFile, [ResType],[ResName],[ResLang] -addoverwrite ResourceFile, [ResType],[ResName],[ResLang] -addoverwrite ResourceFile, [ResType],[ResName],[ResLang] -modify ResourceFile, [ResType],[ResName],[ResLang] -extract ResourceFile, [ResType],[ResName],[ResLang] -delete [ResType],[ResName],[ResLang] on the blogg, yet the comment i got was that, it was 1script file per resource file, so i proposed file sections as: <file = system32.dll> -add ........ -del .... ....etc......... </file> witch can become rather unclean, as well, Thats why i wanted to see what people thought about, also including, the origing file in a command, ofcaurce it would be conf filre rather than a batchfile (you dont want calling patcher.exe) for every seperate file you want patched. but you should get sothing like... patcher.exe -ua:patcher.conf patcher.conf 00: resource patcher configuration file version 0.1 01: 02: <file> <command> <restype> <alocation> <lang> <resource file> (to be discused).... In the end this would just be a batch file, but parsed by patcher rather than by command.com ) ....

Update: the info in this topic should be considered reference material only. it is outdated, and a new topic has be started... < check it here > ________________________ this topic should be clozed..... ____________________________________ In discussion here we've talked about x64 versions of XPize and future Vize, and as XPero has said he wanted to go away from NSIS and I think he should take it a whole step futher. Just recently NTcore offerd to add command line arguments to his CFFexplorer whitch is part of the Explorer Suite these so-called commandline arguments would enable the tool to be used in scripting and thus in installers (like XPize), with this tools you can do almost all resource editing including; hex, bitmap, vista icons, and more, in both 32 and 64bit aplications, but to get it all working he asked for some requests about the best way it should be implemented.. my first idea would be to have both a commandly agument and a config file as below: ;a resource patcher file should consist of the following information, ; a) a sourcefile (an exe or dll that should be patched), ; b) a command (describing what should be done with the file ; # for example ; # >> -add (ads a resource) ¹ ; # >> -update (updates a resource) ¹ ; # >> -del (deletes a resource) ; # >> -save (saves a resource as file) ² ; c) the alocation and name of the resource (example: bitmaps\10245) ; d) (if required): the resource file name ¹ / or destination file name ² ;examples ;system32.dll -update bitmap\1234 c:\temp\xpize\system32.dll\1234.bmp ;system32.dll -save icongroups\1357 c:\icons\1357.ico any commands are welcome, please lets al make it word for x64 users...