bober

good job. :dribble: (on having vanquished teh beer..lol jk nice work)

ah nice !! ok well i'll update when i get back 2 night

make the gui loop like crazy/memory leak, and leave it running,ull have ure self a hot potatoe of a PC!

i was under the impression that only the .txt was enough and any defualt sfx would have worked (cause the txt contains the program to be launched and the paths)but i just tested and ure right,we Do have to use the sfx...my bad also an easy way to compile an 7z sfx on the fly,drop the 3 files in a folder and : copy /b *.sfx + *.txt + *.7z ure_file.exe but im sure im not showing you new stuff.but i do have one question,did you add ure variable and called the setup fromt he 7z gui and compiled it? cause i cant see much in the sfx when i edit it.(thus why at first i was convinced that only the .txt file was enough) EDIT: ok im finished editing the xp exes, i think they came out prety good, lol the install logo that i made cklicable was kinda of a pain, cause stimpy had made them and had alpha channel shadowing,and the way the setup software is made is that it does support it but the result was crap.but i realy wanted the logo to be clickable.i coulda just left in the original buttona nd just add simpy's logo on the background image..which probably would have illiminated the pixelation where shadow was..anyways im planning on includign the new exe's to the batch version. here they are: xp setups.7z huston we have a problem: so i finaly edited and repacked the new releases of xptsp and then tested them... and the setups dont work, they work if the original .exe .ini and support folder are in the root of the disc, but just launching the sfx dosent work ;/ edit i have done soem reading and the %%s should work as long as you are in a NON read-only enviroment.but there is a way around this; simply set enviroment variables, and then run it as a string after in run program... ill try to fix it 2 night but it is realllly geting late and i need the sleep. InstallPath="%%S" ExecuteFile="Setup.exe" works fine if you rename ure archive to lets say xpsetup.exei nstead of giving it the same name(lol we wouldint want a loop here...) 20th edit(lol): ok problem no1: our archive's name is setup.exe were extracting it to current dir..so right there thers a problem(plus the installer canot be renamed cuz for sum reason it dosent like it,but thats no trouble we can easyley rename the sfx instead" 2nd problem:like i said extracting to current dir is no good,but we have to cuz the paths from the setup.ini of then autorun need to be in the root. so i think were prety much focked.(damn ini paths) plus im realy bummed out that i edited the batch files to remove the old autoruns for the new one..was suppsowed to updated releases...i still like the new ones better and prolly will include them anyways... lol oh well.

what 2020?? arent we supposed to die in 2012??

btw i belive you ment: ;!@Install@!UTF-8! SetEnvironment="InstallDir=%%S" ExecuteFile="Setup.exe" GUIMode="2" ;!@InstallEnd@! the sfx only has the icon

its to eventualy support multilang... i guess

well you should try with neutral contents.

here is some info that may or may not help you: [COMMANDS] -delete MENU,,0 -delete DIALOG,,0 -delete STRINGTABLE,,0 -add MyProg_Rus.res, MENU,,1049 -add MyProg_Rus.res, DIALOG,,1049 -add MyProg_Rus.res, STRINGTABLE,,1049 so if u useaddoverwrite and give it the lang code it migh replace the actual item and keep the previous lang id

yeah it does look nice. and yeah, it does make the root folder cleaner. only 2 small fixes are needed: so then we would need 2 more versions for home and mce ok i spent some time on making a mce autorun theme, i might re do pro and home so they also look the same: mce setup.exe

about replacing stuff that dosent have the same lang id,i think ull have to use the delete feature of reshacker then patch. and or determine the lang of the file being patched and attribute that id to the res file or write it batch to the file after its been patched.

dougie, in next release there be 2 new files to be copyed to a xp pro source : blue_ss.dll metal_ss.dll

just a heads up, update iminent in the next few days...

hehaha

amnesia , here' s small token of my appreciation: Amnesia player dug out some old vb6 code i had made for school, its not perfect tho..

hey thx man! now if only every one would use the addon version it would be way better.

which ever seems nicest,but Segoe UI is int eh addon version of XPtsp.

ah well if ure workign on it yeah,thx.

ok ,thx and i mis-red you,lol i edited ure theme for nothing.lolol but yeah ,again, ill have to edit xptsp's to make use of the other windows default themes and make them usable.

ure not limited by what the original luna theme has, here ill upload ure theme that i modded just res edit the different shellstyle.dlls ... winclassic is included in the msstyles ow yeah i should re edit it cause there is some bulk, or atleast we should edit the other shel style in luna..i havitn gotten around this. edit: give me a sec im uplaoding ure theme... ok here are the steps, aero green is normal color aka default color scheme. so u prolly dotn need to edit that shellsyle.dll cause it has ben generated from ure msstyle. for aero blk and blu,there are also defualt generated from msstyles,so just res edit them to their specific color and ure good to go. amnesia_theme.7z

Dougiefresh notes: Quoted post is from here..... Couldn't add to this thread because that post would usurp the original first post of this thread. i can confirm only 1 style, cause u didint incldue ure different shellstyle.dll files in ure Shell folder for Aero Green", "Aero Black", "Aero Blue", "Classic XP". if you include in seperate folder thoses modifications i could maybe help and create ure dlls.

good thinking,i think we should keep it open a few more days and lock it after.

time flies like wind, fruit flies like bananas.

damn, nice!

ok cool thx.