LeveL

Not so fast Arnie got in. Period. Its not about being a politician, its about coming across that way to the people. Ronald Reagan = Actor. Arnie = Actor. I think the USA Government is trying to tell us something, in a coded/sick way, naturally.

Come on, she can't be any worse than Penis Cheney.

Ho ho ho!

There is something you can try (this is to give vmware 64mb of video memory) but it is "experimental" and didn't work for me, you never know though... 1 - Make sure that vmware is shut down (NOT just paused, it needs to be powered off) 2 - Go into the folder where your virtual disk is stored, open the VMX file with Notepad, add these two lines... mks.enable3d = TRUE svga.vramSize = 67108864 3 - Power on the VM and PREY! Allocate all 512Mb to the virtual machine, yeah your real system is pretty much crippled whilst Vista is installing but, once its installed, shut it down, double click the RAM, turn it down to 224Mb (NO LESS) and power back on, this is the great Vista SCAM! The scam being that it refuses to install on anything under 512Mb RAM but runs quite happily (just as smooth as 512Mb) on only 224Mb of RAM, proving that Microsoft are making us buy hardware we do not need.

It installs from the MSI (using /quiet) but there are no shortcuts on the start menu, desktop or quick launch, hmmmm. Its OK I did the old XCOPY trick for the shortcuts

Windows (on my system and I am sure most systems) puts my IDE hard drive on a transfer rate of 33Mb a second. Or "UDMA Mode 2" when the drive is perfectly capable of transfering data at 133Mb a second. I guess its just ANother way for Microsoft to scam us. Luckily there is a registry tweak I put together from instructions on manually doing it that will force UDMA Mode 6. It does this in such a way that IF you do get transfer errors because it is going too fast, it will drop back down again. To be exact, it will drop back down if you get 6 errors in a row. The way MS have it set it drops down if you EVER get 6 errors, they could happen a year apart over 6 years! Please, pretty please, add this "tweak" to nLite? Just under advanced or something if you think it is risky! I don't really think it is risky I mean, on my system I apply it and it will only go up to UDMA Mode 5 which is 100Mb/s. So this means, it does not mess anything up really. Only problem might be applying this to a system with SATA drives since they do not have this problem. Give it time, I am sure Vista will be the same with SATA as XP is with IDE, dropping the transfer rates right down for no reason apart from to annoy us. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001]"MasterDeviceTimingMode"=dword:ffffffff"MasterDeviceTimingModeAllowed"=dword:ffffffff"SlaveDeviceTimingMode"=dword:ffffffff"SlaveDeviceTimingModeAllowed"=dword:ffffffff"ResetErrorCountersOnSuccess"=dword:00000001"MasterIdDataCheckSum"=-"SlaveIdDataCheckSum"=- [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002]"MasterDeviceTimingMode"=dword:ffffffff"MasterDeviceTimingModeAllowed"=dword:ffffffff"SlaveDeviceTimingMode"=dword:ffffffff"SlaveDeviceTimingModeAllowed"=dword:ffffffff"ResetErrorCountersOnSuccess"=dword:00000001"MasterIdDataCheckSum"=-"SlaveIdDataCheckSum"=-

What about RC8? If you're gonna compare them that is Nuhi, the amount of work that must have gone into nLite, I think you should sell it! Yeah maybe this goes against what its all about but, I really value nLite, it has to be the best free program there is. Period.

Nuhi please don't ever put in an option to auto partition! Or if you do, hide it away so I can't accidentally tick it @ ravenz - It is only a case of changing a 0 to a 1 in I386\WINNT.SIF [Data] AutoPartition=1 Just don't blame me if you accidentally boot from the ISO one day

This is a challenge thats why we should do it I tried to do it - I stripped 2000, XP and 2003 but left in the upgrade options. Then made the boot files etc to do multi-boot and it ended up not working, but you can fit 2000, XP and 2003 on one CD, trust me I did it, but it wouldnt install in the end. The problem is that the source files in I386 ended up being different to what was in txtsetup.sif, or something, can't quite remember why it didnt work. It makes me laugh when people say "why would you wanna". It should be about doing it, not asking "why do it". I have to ask "why not do it".

Yeah, but it isn't legal

Not a problem as such but I tried to UniExtract PhotoStory3.exe (it came out of an MSI file to belin with) and get this... C:\__\__\__\PhotoStory3.exe cannot be extracted. Filetype returned was: Nothing found Seems Microsoft have some compiler all of their own? Also, there is a virus scanner that claims to scan within ASprotect packed executables. It would be a GODSEND if those could be unpacked! Many viruses are put in those ASprotect files because they are really hard to crack open. The virus scanner that claims to scan within them is called "Virus Chaser". It can also scan within UPX EXE files.

I also tried this - doesn't work Tried with nLite RC8 which has this listed under the registry tweaks on a Server 2003 OS (which I must say was a great sight) but nLite wont remove it either! Why do Microsoft insist on making life difficult for administrators? I mean, is there an actual reason? Are they satanists, or what? EDIT: Sorry ignore this - IT DOES WORK! Nice one Sonic I still maintain, however, that Microsoft are a bunch of satanists. B)

Is there no registry solution to this at all? Searched the forums (but it would help a lot more to find this if this topic said "Server 2003" and not "win2003" ) It seems to depend on the display adapter that is in the system? If that is the case, I guess it is impossible to turn the hardware acceleration up to full with a registry tweak? Hmmmm, OK then the next question is - what command or what exe in system32 will bring up the screen: Right click Desktop then... Properties > Settings [tab] > Advanced [button] > Troubleshoot [tab] If I can find which exe to run, or a function in a DLL or something, from a command line to at least bring up the "Troubleshoot" screen, I can write an AutoIt script then and hey, I will give it away here, lets solve this stupid problem once and for all!

I think somehow I was making the main Administrator "Server2003" because in Documents and settings, there is no user called "Administrator", just Server2003/All Users/Network Service/Default User etc, I have show hidden folders and show "super hidden" folders all enabled. Thanks for the suggestions, I will have a try with your NT script! If I can't get it to work, I can just stick with the older SP1 I guess, updates can be installed silently with the /Q /O /Z switches for most of them, I can't see there being that many updates anyway

Just in case anyone wants those magic tweaks, here... Windows Registry Editor Version 5.00 ;Disable Manage Your Server Wizard on Startup [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Setup\Welcome] "srvwiz"=dword:00000000 ;Enable DirectDraw and Direct3D in DirectX Diagnostic Tool (install your graphics card driver to see this change) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectDraw] "EmulationOnly"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Direct3D\Drivers] "SoftwareOnly"=dword:00000000 ;Set Programs so they have priority over background applications [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\PriorityControl] "Win32PrioritySeparation"=dword:00000026 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management] "LargeSystemCache"=dword:00000000 ;Disable all "Ctrl+Alt+Del" prompts (login, resume & standby) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system] "disablecad"=dword:00000001 ;Start Themes Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Themes] "Start"=dword:00000002 ;Start Windows Audio Service [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\AudioSrv] "Start"=dword:00000002 ;Disable Shutdown Event Tracker [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Reliability] "ShutdownReasonOn"=dword:00000000 "ShutdownReasonUI"=-

Yes it is, extremely different in my experience. Server 2003 is soooooooo locked down that you will need to invest a good deal of time learning how to make it work for you. It arrives in "ultra-paranoid" package mode. Good luck. Aaah but, I already had all that sorted out, like enabling Windows Audio service, don't show "Manage your server" wizard, the whole lot, with a registry file. Just seems bizarre how I had it working before and all I wanted to do was integrate the latest SP1 because the old SP1 1210 was a beta version of the service pack. Never even had any trouble with it either, all I can assume is they made it even more secure with the later service pack or something?

Can anyone help? I know this is "Server 2003" but sheesh, its not that different to XP! I had this all working ages ago, came to do it unattended again and it wont log in with the newly created account (created silently @ t-12 with cmdlines.txt and the useraccount.cmd script with the autologon.reg) Read the 1st post! You can see what does what and how it all (should and DID in the past) works. The only difference is now I have integrated SP1 1830 and in the older one I used SP1 1218... so is it some sort of "extra security feature" of SP1 1830?

Is there anybody out there?

Trying to make Server 2003 unattended, for some reason what has always worked in the past is not working now. I want it to autologin with a blank password (so then it is truly "unattended") and so, I cannot use the user "Administrator" so I have to create a new user at the t-12 minute stage with cmdlines and an NT command script. Its like this (remember, this has worked in the past!): Unattended setup runs cmdlines.txt... [COMMANDS] "useraccounts.cmd" This runs useraccounts.cmd... net user Server2003 /add net localgroup Administrators Server2003 /add net accounts /maxpwage:unlimited REGEDIT /S autologon.reg EXIT This runs autologon.reg... Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="Server2003" "DefaultPassword"="" "AutoAdminLogon"="1" Now it comes to the log in window, which should log in automatically and always has in past installations, it says "Server2003" in the username box and blank password. I hit OK without typing a password and it says it could not log me on! So I type "Administrator" and hit OK (again no password) and it does log me on, however the rest of the setup is designed to copy stuff to the user "Server2003" (who is AN Administrator but not THE Administrator) I have my WINNT.SIF set up right, its worked in the past, here are two of the sections where the password would be and the new users account details... WINNT.SIF [GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO OEMSkipRegional=1 OemSkipWelcome=1 [UserData] ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="Server2003" OrgName="Home" ComputerName=* The most annoying thing is, this has worked in the past and it used to autologin, this is what the useraccounts.cmd and the autologin.reg files are there for. The only difference now is I am using build 1830 of service pack 1 whereas in the past, I was using build 1218 of service pack 1 (slipstreamed in both cases, one case works the other does not) but I don't see why the build numbers for SP1 should have anything to do with it? Grrrrrrrrr!

I did do it somehow and it was the CALL function that was needed after all. Last line of WINNT.SIF says... CALL "%PROGRAMFILES%\bbLean\start.cmd" EXIT Hmmmmm, actually thats the last line of NLITE.CM_ which is really what WINNT.SIF points to at the end, its complicated but, possible in the end. B)

"Batch files can be re-used effortlessly" oh sure, gimme a break! Seems 1900 others are stuck too..... "Cannot find C:\Program" EDIT: this works....... CALL "%ProgramFiles%\Folder\install.exe" But only because I managed to make an AutoIt exe with an NT command line contained within that! So thank you AutoIt2.... YOUR STUFF WORKS unlike Microsoft, which I gave up with.

If only it were that easy! I put this..... start "%PROGRAMFILES%\Folder\script.bat" pause The pause is just to see whats happening, when I do this I get another DOS window with the window title... C:\Program Files\Folder\script.bat And the text, oooooh that famous text... C:\Documents and settings\Administrator\Desktop Like it is CD'ing to that DIR? Yes, I am currently trying to run this command from the Desktop and get it giving me a command window on the desktop! So lets get it straight... it is not doing what I am telling it to do and at the same time, is doing something quite useful IN ANOTHER SITUATION but not this one It ALWAYS does this! I do not want a ******* console window on my Desktop! Anyone would think I typed........ cd \%USERPROFILE%\Desktop Because thats exactly what its doing, running another console window in the same place as the first, so it opens on the desktop. It has always done this, for the 2 years I have used scripts and for the next 2 years by the look of it, believe me I have tried to sort this out before, its impossible. Why is it always ridiculous things that should take 5 seconds to work, you'd think, that take hours or even days to find an answer to? Nothing wrong with this..... %PROGRAMFILES%\Folder\Script.cmd But it opens a console window on my desktop, how sweet! Shame when there is a script in Program Files I wanna run and that is precisely what I told it to do, but nevermind. When has Windows ever done what you expect or tell it to do... I would get further with a pocket calculator

I have a CMD file, lets call it "script.cmd" That is in a folder in program files, lets call that "Folder". I run this command from winnt.sif, you all know where that file is .............. %PROGRAMFILES%\Folder\script.cmd And it will not work! I was annoyed hours ago, now I am just gonna scream or chuck my PC out of my window! NOTHING WORKS. Why are they called "batch files" if you can not run one file from another? Aaaaah - use the CALL function? Nope - refuses to work...... How the hell M$ managed to develop Windows with this pathetic command language is beyond me. You know why my script is inside Program Files and not in C:\install like everyone elses unattended setup and every other unattended setup I have done in the last 2 years?! Because, then I can't install the program that is in program files! Isn't that just beautiful! I have to have my entire unattended inside this ONE folder in Program Files, so as you can see, it is a JOKE to begin with, and its getting funnier and funnier as I go along here. This won't do it.... CALL %PROGRAMFILES%\Folder\script.cmd This wont work either.... CALL%PROGRAMFILES%\Folder\script.cmd Or these after renaming to BAT... CALL %PROGRAMFILES%\Folder\script.bat CALL%PROGRAMFILES%\Folder\script.bat No wonder the whole of the internet uses Unix.

http://www.msfn.org/board/index.php?showtopic=73272

I tried LiteShell (a replacement for explorer.exe) and now I get this error, note that the error is the same each time but, with a different number. This does not refer to any missing DLL Why cant XP just TELL ME WHY? Now all the shells do this, bbLean, Litestep, Aston loads explorer, they ALL still load explorer no matter what. This happens on a full clean install of XP when trying to explore from within another shell...