Jump to content

Godfatha

Member
  • Posts

    51
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by Godfatha

  1. Just as a question (for anyone that is maybe a bit longe raround this forum than i am). I could maybe post the whole instruction for doing cds this way and the mutiboot dvd, but would i have to post it in two different posts or threads? since there's also a multiboot dvd forum i better ask before it'd get moved or deleted or whatever. It'd be easier to post only once, since i could refer to the lines i allready wrote and the guides of gosh and flyakite. else i'd have to link to my other post(s) if i'd have to post 2 posts... thanks in advanced.
  2. on the cds i have only one i386 folder (well on 2k server there is also the clients folder but thats just on 2k so) and on the multiboot dvd i have one folder for each system at least 2 times (like 2000 and 2KUA for the normal 2000 installation and the unattended one and that for XP Pro/Home, 2000 Pro/Server and for 2003 Server) well since we still have to install it at work i have also a ghost.ima in the root and one folder called Ghost that contains preinstall images of Windows 98 and ME and Partition Magic 8 as well as Erd Commander 2002 (yeah i know there's a 2003 version but we don't have a license for it, so we go for 2002)
  3. Just to let you all know, i solved the problem. the OEMfilespath thing doesn't work and i doubt even MS theirselves know it.... (cause their descriptions always point to other documents that WOULD descibe it in detail, what isn't true) i packed everything on CD, like \INSTALL\UPDATE** (where the ** stands for 2K, XP or 2K3). i deleted the $1 folder from my distribution folders and in the cdmlines.txt i added only one batch file checking for 2 significant files to deside whether you run a XP, 2000 or 2003 installation. After it desided what is running it imports the correct registry entries for run/runonce/runonceex or whatever you want your system to have integrated. Since i am a nice guy (hehe...) i'll paste the cdmlines.txt, the init.cmd and an overview of my folders: cmdlines.txt [COMMANDS] "init.cmd" init.cmd: CLS @echo off TITLE Windows Unattended Installation post install initiation IF EXIST D:\CD.txt set CDROM=D: IF EXIST E:\CD.txt set CDROM=E: [...] SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REGEDIT /S autologin.reg IF EXIST %systemroot%\system32\reg.exe (GOTO XP) ELSE (GOTO 2K) :XP IF NOT EXIST %systemroot%\system32\mspmspsv.dll (GOTO 2K3) COMMANDS.... GOTO EOF :2K COMMANDS.... GOTO EOF :2K3 COMMANDS.... GOTO EOF :EOF EXIT The folders: \ |-$OEM$ (holds the $$ directory to copy all important stuff to my windir) |-OEM (holds the drivers to be installed from cd) |-INSTALL (All updates and programs to be executed at first (second) start) |-UPDATE2K (hotfixes for Windows 2000) |-UPDATEXP (hotfixes for Windows XP) |-UPDATE2K3 (hotfixes for Windows 2003) |-... |-... so if i would have to add something, or change something whatever... i have central directories that i have to change only once, not for every install one folder... maybe someone needs that so thats my idea of handling it...
  4. I got the same, i solved it like that: after the setup is done start.cmd is executed via the guirunonce in the winnt.sif, it contains only three things: the IE6 Setup and the import of RO.reg (to logon automatically and to place a runonce key for a second batch (start2.cmd)) . When its executed, it installs IE6, imports the regkeys (they have to be expanded regkeys if u use variables) and the uses shutd0wn.exe (which i copied from a winxp install to my $oem$\$1\system32 folder to make it work) with the option -f -r -t 3 Next time the PC starts up, the second batch is executed that does the rest, THEN the install works properly with no errors. start.cmd: CLS @echo off TITLE Windows 2000 SP4 - Unattended Installation IF EXIST D:\CD.txt set CDROM=D: IF EXIST E:\CD.txt set CDROM=E: [...] ECHO. ECHO Installing IE6 SP1 ECHO Please wait... start /wait %cdrom%\install\ie\IE6SETUP.EXE /q:a /r:n REGEDIT /S %systemdrive%\install\RO.reg ECHO. ECHO Restart %systemroot%\system32\shutd0wn.exe -f -r -t 3 -c "Dieser Neustart ist sehr wichtig!" EXIT start2.cmd: CLS @echo off TITLE Windows 2000 SP4 - Unattended Installation (2/2) IF EXIST D:\CD.txt set CDROM=D: [...] ECHO. ECHO Installing IE6 Patch 1 of 8 ECHO Please wait... start /wait %CDROM%\install\updates\q330994.exe /q:a /r:n [...] RD /S /Q %systemdrive%\Install\ EXIT RO.reg: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce] "Setup2"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,44,00,72,00,69,00,\ 76,00,65,00,25,00,5c,00,69,00,6e,00,73,00,74,00,61,00,6c,00,6c,00,5c,00,73,\ 00,74,00,61,00,72,00,74,00,32,00,2e,00,63,00,6d,00,64,00,00,00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "AutoAdminLogon"="1" (the "Setup2"=hex(2):25,00.... is the expanded reg key to make the runkey take the variable %systemdrive%, it means: %systemdrive%\install\start2.cmd) the other way to make it, would be using Reg.exe, what isn't available in the normal windows 2000, if u want to use that, read about it somewhere in this forum. thats basically the stuf i did to make it work...
  5. Well, i tried to install everything from the cd allready. the contents of my $OEM$ folder is: \updates and \IE IE = IE6 SP1, that CAN be launched from CD. Updates = several updates for: WMP, Windows Media, IE6 SP1, OE, MDAC & for Xp advanced networking pack Some of these Updates cause errors while installing from the cd, my guess would be MDAC, but i got also errors on at least 2 IE updates (after too many errors i stopped the installation and retried it by copying them to the hdd and install from there, what caused no errors at all) That was the reason i kept the OEM dist folders instead of making it without it.
  6. I've read about that, but the folders would have different files (like windows 2000 would have the IE6 SP1 package, 2003 wouldn't) If there's reall no other way, i'd have to go the way with the -o option..
  7. In the windows XP/2003 setups you can launch more then one (at least two like i do), in the windows 2000 setup i wasn't able to launch two, there i was able to launch only one.
  8. Hi there! I have one big problem to solve out. I made a couple of unattended CDs, which all work very fine, but since i wanted to put all my cd's on one DVD one thought came into my mind: Where to put the OEM distribution folders? Hell yeah, i make one folder for each windows Version (Windows 2000 Pro/Server, Windows XP/Home, Windows 2003 Server Standard). Said and done. My CD (not dvd, cause i wanted to try it on a cheaper cd first) content would look like this: the folder for the $OEM$ (lets say \2003) in it the $OEM$ the i386 Folder (we all know it) the install folder (for installations made from the CD) the OEM folder (NOT $OEM$, this contains the drivers, installed from the cd, so the setups don't have to copy 200MB to the harddisk and i have one folder for ALL setups the same) the hotfixes folder (called Update2k3) the thought about it was: the setups have their own folders, but if i install 2000 Pro and 2000 server from one medium it would take double the space to add a $OEM$ folder to each installation (same with the hotfix folder). The hotfix folder works excellent by adding this to the dosnet.inf: [OptionalSrcDirs] ..\Update2K3 and this to the SVCPACK.inf: CatalogSubDir="\Update2K3" so last thing to do is getting the $OEM$ thing working. Windows 2k b*tched at me, it wanted a $OEM$ folder in the CD root only, and i had to point to it via the entry OemFilesPath="$oem$" in the winnt.sif, nothing else worked. well i thought as long as the others setups take another folder (like \2003\$OEM$) its not that bad... so i tried in windows XP and 2003 this: (example is from 2k3, the folder was in the root of the CD called \2003 in it the folder \$OEM$) OemFilesPath="2003\$oem$", OemFilesPath="..\2003\$oem$", OemFilesPath="2003", OemFilesPath="..\2003" none of these worked! BUT if i put the $OEM$ folder in the root of the cd, i can set these two: OemFilesPath="$oem$" or OemFilesPath="..\$oem$", both work (i have no clue why both work, but somehow setup seemed not very interested that the entries would point to different paths). I hope anybody know how to do this, to mention it, it HAS to be a folder on the cd/dvd, not a network sharepoint. And the folder structure would be like that: \2003\$OEM$\ \2000\$oem$\ \XP\$oem$\ Thanks in advanced.
  9. still the OEM dir, cause you want to run the batches from the CMDLINES.txt which is also located on the OEM dir. The Winnt.sif isn't changed either, well only if u install drivers from cd u skip the pnpdrivers part out.
  10. I'm not sure if i understood that correctly, but you want to change the way your files and folders are listed in your windows? If so, open a folder and configure it how it should look, then open the "folders options" i have no english windows either, so i hope thats correct (its where you can configure to see hidden files etc) and tell windows to make all folders look like the current. then close the window, restart. Open the registry and browse to: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer] and export the infos of this key and the subkey Advanced (not the other subkeys, i'd not mess with those) if u just export that, open the regfile afterwards and delete everything that does not belong directly the the entries i pasted above. I am not sure what every entry means, but if i import both keys on a new installed system i have my old folder views back Yeah the thread alanoll pasted is correct, the streams do the listview things, sorry i was at the show hidden files etc. i forgot that i import the streams too...
  11. i've exactly the same problem and i found no solution then to skip the restart. well you could make a batch file that has a pause command in it, but then you would have to press enter after the setup is done. I have the problems on Office2k and on Acrobat 5, both setups run in the background and the other setups run parallel. the thing i did was to install first all updates/hotfixes that i wasn't able to integrate in the svcpack.inf (IE SP1 and all updates for it, MDAC, WMP Patches etc..) then i install the apps that do everything correct and as last but 3rd office and as last but one Acrobat 5. then windows starts up, the setups finish (office gives you a message that its finished and acrobat places an icon on the desktop), then i manually restart.
  12. Configure your whole Desktop, save the Desktop Theme file. On your windows installation you create that Folder: $oem$\$$\Resources\Themes In it you copy your theme file. Then you change your Winnt.sif like that: [shell] CustomDefaultThemeFile = "%SystemRoot%\Resources\Themes\Standard.theme" just add those two to the end of your file. Then burn the cd and install from it, after the setup windows should look exactly the way you saved it before.
  13. Remove those two lines: NetMtg = Off MovieMk = Off i wasn't able to find any reference to thoses components, the others i was able to find. And i don't think it was caused by the spaces, but i had the problem, that i left a blank line in the TXTSETUP.SIF and setup asked me to insert the Windows cd after the Press F2 for system restore....
  14. To copy your icons, use a folder called $docs in your $OEM$ folder and create a folder callled "All Users" in it. In the newly created folder create a Folder called "Desktop" or if its 100% sure that the desktop folder is called "Skrivbord" in your version call it like that. in it you place your icons. The second Problem: that one is correct "$oem$\$1\drivers", but every folder you created in there, that contains driver files (like e.g. "$oem$\$1\drivers\vga" or "$oem$\$1\drivers\Sound" or something like that" has to be in the Winnt.sif file, and you have to seperate the folder pointers with a semicolon like that: OemPnPDriversPath=drivers;drivers\VGA;Drivers\Sound;.... after the last entry aou do NOT place a semicolon! Make no spaces and do not press enter while listing those directories. then all should be found. And to the files that are Compressed: decompress them (Expand FILE.EN_ FILE.END) or use winzip/-rar/-ace to decompress them. I am not 100% sure but it could be that windows does not find them, so just put both in the directories, the compressed and the decompressed then everything should work.
  15. I am not 100% sure, but if you try to launch programs out of a html file, it will always try to download it. And even if you say execute it would try to temp download it. The links in the windows help are in the help files, you could use programs to generate a help file (i don't know which programs can do so) and launch that instead of a html file. That should do the work...
  16. You gotta edit the winnt.sif so far, that you leave every configuration to the user (use the setupmgr to create such a file, just follow the instructions and do it). afterwards u put in the file the line: [unattended] ... OemPreinstall=Yes ... Then you put your cmdlines.txt in the $OEM$ folder and it has to look like that: [COMMANDS] "COMMAND1" "COMMAND2" .... do not forget the "" those are important. that should do it.
  17. If you boot up with a boot disk (as you said) the boot disk creates a ramdrive (it maybe does). The normal Windows bootdisks do so. After the setup starts, the Ramdrive should be present in the dialog where you choose the partition to install. if that is the case, change the disk to make it set the ramdrive to R: or you just delete the ramdrive stuff and try it again. Because if the setup restarts, the ramdrive ain't present anymore, the Drive letters should have changed but windows is looking for the path it saved before. Maybe thats the solution for your problem. If you boot up with the cd check out your partitions, maybe you have to repartition somehow. I kinda doubt that, but maybe there is something wrong. Or if the setup can't find files, but it found them before, maybe the cd or the cdrom drive is failing and due reading errors files can't be found.
  18. i am not 100% sure but the registering components is where the svcpack and cdmline is executed, maybe you have added all hotfixes and Directx etc to your cd and it takes just a freaking long time to install all of those patches.... I know that some pc's took like 45 mins to pass the 13 min phase of the xp setup, typacally its like 15 mins. I also had pcs that only took like 10 mins but also one that took the half day. If you're sure its not caused by that, make sure that the pc doesn't hang (move the mouse and see the courser moving). and if nothing helps, try an unmodded xp version, if that works you gotta change something in your mod. if that does the same the problem is caused by something else (Hardware problem maybe)
  19. you would have to make something like that: [Data] AutoPartition=1 ... [unattended] Repartition=No/Yes FileSystem = ConvertNTFS ... so, autopartition = 1 will make Windows choose the partition to install on. there are some rules on what windows chooses its partition. In the normal case windows always installs itself on C:\ i have never heard of something different. but the way setup detects c:\ is the strange part. typically c:\ is the primary partition of your drive, but windows could also interpret an extended partition as c:\ if the primary partition isn't created. Or if the extdended Partition is active and the primary ain't. But if both are active it chooses the primary one. same for having 2 hdd's, if the first has no partitions created but the 2nd hdd does the c:\ would be (typically) on the 2nd drive. the other cases like on the 1st drive are non active but on the 2nd normally causes windows NOT to choose the active partition from the 2nd drive, but the primary of the 1st drive. I know it's kinda strange, but those cases i've seen at work, so it seems that windows chooses somehow the install-partition on "good-luck". The Repartition switch will cause that the Partitions on the first hdd are deleted (so be carefull) and one big, new partition will be created, that one will be formated with ntfs. I had one case, that the old partitions weren't deleted, but the first partition was deleted, recreated and formated. Note that the partition is not a quick formate... the last switch just assures that the filesystem is kept ntfs and not fat32, you can normally delete that line, i just know that this setup created so far no problems if you make sure that you don't loose your data by Repartitioning....
  20. after you burned the iso to a cdrw you can't just change the stuff on the cdrw, but after you did change your iso file you can delete the cdrw and reburn it. If you want to change stuff on the cd you would have to use it in some mount rainier way that its mounted somehow as local drive, but then it won't be your iso anymore, cause there won't be no bootsektor etc. and a bootable cd has to be finished, and a mounted cd isn't finished, its like a multisession cd, just with direct access... So use your cdrw as normal cd and delete its content after you changed your iso file and reburn it, its the best way...
  21. Like i guessed, it was a good thing not to try windows without user accounts... but thanks for the info
  22. yes, the FullName="" just adds the license owners name, in your case your name to the registration of Windows. To add a user account follow these instructions: http://unattended.msfn.org/xp/autologon.htm and if you don't want the windows welcome and "please register now" pages after the setup, add UnattendSwitch="yes". But do that only if you added a user account or if you logon as administrator aftre the setup. I didn't tried out what will happen, but since we're talking about windows i doubt it's a good thing...
  23. I am not really sure what the variables in the winntbbu.dll mean, well the font description stands for the font, but you can't change the color from those variables. The only thing u could do to change the color of your texts is to open the file in a hexeditor and search fpr the color codes. The color codes look like the ones in HTML, so if you got white text it would be FFFFFF, black would be 000000 etc... The problem that you will encounter is, that there are many FF's in the file but in my case it was like there are a lot of FF FF FF FF, as you should see there are 2 too much. So what you could do is the following: Open your winntbbu.dll with a hexeditor and perform a search for a hex value FFFFFF (6x F) and skip those results that have more than 6 F's. After you found a line that contains 6 F's, change them to your favourite colorcode and save the file (always keep a backup of the original one...). then copy it to your i386 folder and run the Setup, if you get an error, you changed the wrong values, if the color is still the old one, you changed the wrong values... It took me 4 tries to find the correct line, so far windows Setup caused 2 errors and one time nothing happened. Hope that helps...


×
×
  • Create New...