Alanoll

Like i said before, if nuhi were to create such a thing, i'd just prefer it to be seperate from nLite. If everything is in one program, then people will be tempted to try something and cry murder when "the program" screwed up their windows. If i had something against nLite other then the users that sometiems follow it, then i wouldn't have added nLite to the Unattended Guide, or asked if nuhi believed it was time for a full nLite guide... I just wish if nuhi were to make a program to do Applications and such, that he would remove the Unattended,Drivers from nLite and create a new application for that purpose. That way if nothing else, if people download the one MEANT for Unattended creation, they wouldn't be tempted to remove components and possibly screw something up.

I don't want nLite to be a program past it's original intention. I would have no problem if nuhi made a seperate program, and kept each module different from eachother. The problem i have with programs doing everything for you, is that they do everything for you requiring no thought. While at times, this can be helpful....it has the drawbacks of idiots coming and using it and screwing up everything and then complaining. I'm a STRONG believer of nLite being just a stripper and nothing more. After all, it's name is nLite! I have no problem of using multiple programs to do something. Form follows function. nLite's original function was stripping and should have stayed as such in my opinion. The main problem i have with nLite though is NOT that it does what it does, and more then what it's name implies, but purely the people that it brings that want everything done for them and don't want to do anything for themselves.

arrogance. and no it's not. and i hope that it NEVER will be.

The change was made in SP2, and EVERY hotfix containing TCPIP.SYS there after includes teh limitation. HOWEVER, you're missunderstanding the limitation. The limitation puts NO limit on the number of connections you can have open. It merely puts a limit to the number of connections that can be opened in ONE SECOND. This should have NO effect on P2P or Online Gaming. The application should get a connection refused if nothing else and most likely tries again later on. If this REALLY bothers you, google search for "Event ID 4662 TCPIP.SYS" and there is a hack program to up the number.

i mean modifying... i should point out, that the CMD method i put above could get tricky depending on how you call the CMD. If you're someone who calls the CMD via CMDLINES.TXT, then the %CD% isn't the proper directory anymore, and you must know the complete path to the HTA file. If it's executed via Autorun.inf, it works fine. I could make it more complicated to find out the drive lettering and such, but then it owuldn't work on Win9x. I suggested the CMD trick primarily for reasons of system lockdown. If you go the registry method, the paths to the actual executable may not be right

one moment while i download WPI... start "" C:\WINDOWS\system32\mshta.exe "%CD%\wpi.hta" works. MSHTA needs the full path to the wpi.hta file. %CD% is "current directory" and should work in most instances, unless calling the CMD file from another directory. If it runs via Autorun.inf, then it will be fine. Another method, though I'm not sure of how it would work is .\ This is just a work around to the registry problem, because of rights restrictions and such. Also, C:\Windows = %systemroot% and %windir%. I don't believe %systemroot% is available on a 9x system, but %windir% should be.

the simple think to do, would be to actually call the mshta.exe file rather then the HTA file directly start "" C:\WINDOWS\system32\mshta.exe "wpi.hta" Sort of thing...

wow... you claim to have read the forum rules, yet you failed to adhere to one of them in TWO instances. This leads me to believe that you DON'T read the rules, and that you DON'T follow them. Maybe it's just me, but i don't know... That's two threads violating this rule, opening up for discussion such action taken by a moderator. Now as for the reason why your two AutoXP2006 threads were removed... The first thread as stated above was evidently illegal. Not only were you distributing a Windows XP image, but also providing a VLK key and including a corporate version of a commercial application. The second thread was would have stayed if you had not offered to distribute the package. I very plainly saw XPize work (System Properties, main logo on left) and even XPero pointed it out to you. I deleted the thread because you did not give credit where credit was due. Now in accordance with the rules, this thread is now closed and any future thread related to this will be promptly deleted when i see it. Again, let me reiterate the forum rule

RunOnce itself doesn't ahve that capability to do it. RunOnce\Setup on the other hand can give you the effect you're looking for.

Not advised... if you deleted it, everytime the system starts with the CD in the drive, it will boot to setup, and since the CD has to be in the drive for the second part of setup, it will never get there since it will go back into txtmode setup (the blue screens)

Great work BTS It looks better than unattended.msfn.net (white background, nice font, in one word : "the professional touch" ) <{POST_SNAPBACK}> Man...now everyone is going to think i was copying you Bashrat....

I would hold off on that for a bit more....I have something in the works for the Unattended area of the site.

you made it wrong. I just created a multiboot without 2003, and ERD Commander 2005 worked fine. (And i rewrote that guide that's on his site a few months ago)

You don't need to include the 2003 Server on the CD to get ERD Commander to work. You forgot some file it was looking for to recognize the disc. ERD COmmander brings ALL needed files with it when it creates the original image. So copying 2003 from another disc is NOT NECCESARY.

I wouldn't hold your breath on getting help from many of them. They'll answer questions i'm sure, but i doubt they'll give you detailed information on how to recreate what they did (or in the case of nuhi, opening up the source).

where oh where did you get that??

You're treading on very dangerous ground talking of cracks... And yeah....i still need to write those sections....

my vote is still Catalyst drivers...

if you can show me ONE file that Windows Setup uses that is InstallShield based, then i won't think you're an id***.

My high school had a Mu Alpha Theta (Math Fraternity for High School in the US), that actually had "Don't Drink and Derive" on it...

I could have sworn i told you could delete the dotnetfx folder, but i ALSO said that it won't solve your problem. I repeated myself 3 times to get my point across, and yet you didn't read ANY of them apparently. You could only read the one person who got annoyed enough to put a single word response in LARGE letters for you to get what i said originally.

what about did you not understand????? IT'S NOT COMING FROM WINDOWS SETUP AT ALL! IT'S ONE OF YOUR PROGRAMS THAT'S ADDING IT! Perhaps it's coming from some DRIVER you have installing, perhaps even the ATI driver set including the Catalyst Control Center...

do you have a MCE or Tablet edition? If so, then NO you can't remove it. if you have a NORMAL XP edition, then it doesn't even matter as SETUP DOES NOTHING WITH THOSE FILES AT ALL! Perhaps i wasn't clear on that last time. But there is NO INSTALLATION OR COPYING done by WINDOWS SETUP in regards to the .NET Framework if it is NOT a Tablet or Media Center Edition. Now, one more time, just to be sure... YES, you can delete that folder if you DON'T have the Tablet or Media Center Editions. NO, it probably won't solve your problem, as setup DOESN'T DO ANYTHING with those files. Simply having that folder there, does NOT mean it will install the .NET Framework. Heck, even SPECIFYING to install won't have Windows install it.

for difference, and even screenshots.... head to the Advanced Section, and then Methods on the unattended site. However, i don't recommend you use either till you get the early parts of the site down. The site is broken up in Beginner, Intermediate, and Advanced for a reason. I advised keeping with it.

On a Windows CD (minus MCE and Tablet editions) the .NET Framework is ONLY located in the dotnetfx folder in the root of the CD. If you find it ANYWHERE else on the disc, either YOU added it there, or you got the CD who DID add it there. That's all there is to it. Trust me, i've torn the Windows CD to pieces.