Jump to content

andregcasal

Member
  • Posts

    196
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Portugal

Everything posted by andregcasal

  1. Well, you got a point about the price. It's not worth while, so buyers, forget Server 2003. For the rest of you, listen: Pros: - Better overall hardware managment than XP - All the benchmarks and threads i've seen point that Server 2003 is better than XP (everyone has the same opinion, just search), especialy in graphics (can they all be wrong?). Unfortunatly i've just managed to find Brasilian/Portuguese benchmarks, so you have to use an online translator to understand it. Here's one of them: http://www.forumpcs.com.br/viewtopic.php?t=98039 - Obviously it can serve as a Server (sorry about the redundancy ) much better than XP - More stable Cons: - Price. Server 2003 is expensive. - Can EASILY be converted to a workstation: http://www.msfn.org/win2k3/ (although easily, doesn't mean isn't bad, so it stays in the Cons section) First of all, crahak, I see you definetly stay with XP. But that's no reason for trying to bring Server 2003 down. Most of the things you sayed are exagerated. We aren't figthing to the death about which's faster, just discussing, comparing facts. Next time, please present us with normal-emocion writting. You say it's easy to make benchmarks lie. That may be rigth (really don't know), but why would anyone in it's rigth mind do a thing like that? (Unless they wanna defend XP to the death, of course...) And most important of all, why so many? About software compatibility, I don't see any reason why Server 2003 would be less software compatible than XP. Many games and software are written for XP, but bear in mind that Server 2003 have everything XP does, it just has some features turned off (and other on) for better working as a Server, thus making some workstation tweaks necessary. About "More complicated/more options and other things like that". In first place, most people who even knows about Server 2003 knows his way around OS's. But that's not the case. Server 2003 once turned into a workstation it's about the same thing. So please post facts, not beliefs, so we can consistently measure both performances.
  2. See things this way, Server 2003 is exacly Windows XP but more updated, more secure and with the workstation features turned off. By turning them on, you have a Windows XP Professional but with all the new and cool features from Server 2003 If you search a bit you'll find that all that's needed to transform Server 2003 into a Workstation is registry tweaks, so we don't actually add software nor install files or anything. Just turn on the workstation features But it would be nice to see a definitive benchmark comparing Server 2003 Workstation to XP.
  3. Well, i supose you could run BTS's DriverPacks from WPI. Just make WPI point to the CMD file that runs BTS's DriverPacks. But i'm pretty sure no one did that before
  4. Server 2003 is faster than XP in everything, graphics, memory managment, HD, really everything. It has a better kernel and is made for speed - servers need speed Benchmarks don't lie
  5. Yeph, it seems so I don't know for sure, but that's one of the MSFN users said And I believe him!
  6. Hi RuMor! Well, i've seen plenty of DVDs like that, available to download, but as you may guess, they're all ilegal, including serials to install automaticly and everything. Maybe you are searching in the wrong place. Try www.piratebay.org. Me and many users out here are making multi boot DVDs with plenty of OS's in them, with great features, ones better than others, ones with some emterprise-purpose in mind, other just for fun, etc... I'm planning on making this multi boot DVD: Windows 95 Unattended Windows 98 Second Edition Unattended-Hide Windows XP SP1 Unattended-Hide Windows XP SP2 Unattended-Hide Costumized Windows Server 2003 Standard Windows Server 2003 Standard Workstation Windows Server 2003 Web Windows Server 2003 Enterprise Windows Server 2003 Data Center Win PE (or Bart's PE) Linux Kubuntu All with BTS's DriverPacks. So many drivers in here... All with all hotfixes to date, except for XP SP1 - built for speed. All with Windows Post-Installer that let's you choose what software (plenty) you want to install. Plenty of utilities to format, partition, fix, defragment HD. HD tools such as SpinRite And maybe some more features. So as you can see, this may be one of those DVDs you are talking about, of course sharing these DVDs is ilegal But so many people do it...
  7. Hi T D! Afaik cmdlines.txt only executes if OEMPreInstall=Yes (in the winnt.sif). I don't want to use $OEM$ folders because in a multi boot DVD they apply only to that OS. I'm trying to make a multi boot DVD where you can install files to all OSs, using the same source. Installing software directly from the CD/DVD. That's why i don't want to use OEM folders
  8. Thanks mzar720! I'll be updating this guide very soon, maybe even extend it to a complete "Making a multi boot DVD" guide. I hope it can help many people Regards, André Casal
  9. Hi T D I've read your post carefully in the first time. And my answer to your post remain the same. Thanks for your answer but i don't want to use the $OEM$ folders. RunOnceEX requires $OEM$ to work and I don't want to use them, plus my real problem was getting svcpack.inf to execute files, which i finally could manage to solve. I had this code inside my old svcpack.inf: I kept trying to solve my problem my trial and error and discovered that what i needed was this: So, my problem is solved. Thanks everyone!
  10. Many programs need Framework 1.1 even if 2.0 is installed, because Framework 2.0 is diferent from Framework 1.1 and it's not suposed to replace it. André Casal
  11. Hi all! Pool results: There was a pool on if I should update this guide with the latest Window's or leave it as it is. I would like your feedback. I will be updating this guide soon to add support to Windows Vista and Windows 7 aswell. I'll update all the software to the latest versions and include Graphical User Interfaces instead of text user interfaces. Also I will try to add some software to cut down some steps, to make your life easyer. This is the most complete and updated guide on how to build a Multi Boot DVD with pre-Vista versions of Windows. I'll be updating it as i can. Hope you like it changelog May, 13 (2010) Understanding the boot process timeline is now more comprehensibleGuide clean upAug, 18 (2009) Updated linksSome minor language fixesAug, 20 (2007) "Add an Unattended option" fix (thanks to ysfozy)Jan, 13 (2006) Automatically create multi-boot folders and filesAdded improved and shorter RunOnce.cmd codeAdded the eXPander utilityGuide clean up and updateSep, 15 (2006) Added Windows 98 supportSep, 10 (2006) Fixed offline links, since Flyakite's Multi Boot Guide's offline.Fixed spacing and added color for easier readingMay, 21 (2006) Added "CDShell.ini" attachmentCreation of this guide Features in this guide: - Automatically create multi-boot folders and files - Install all your software directly from your CD/DVD (so it won't be copied to the HD, saving time) - You'll have just one Install.cmd file to update and maintain all your software - Determine which software gets installed in which OS - Still be able to use the OEMPreInstall=Yes and [GuiRunOnce] in winnt.sif to launch some other stuff that you may need - You can slipstream drivers to every OS you want, having only one copy of them - You'll still be able to use any post-install methods you like (RunOnceEx, kTool, WPI, WIHU, XPlode, whatever) This guide is compatible with the following methods and tools: - nLite - RyanVM - HFSLIT - BTS's DriverPacks (Method 2 is required in order to have just one copy of the drivers and slipstream them to all the OS's.) - Windows Post-Install Wizard (WPI) - kTool - WIHU - XPlode This guide is compatible with the following OS's: - Windows Server 2003 (Standard, Enterprise, Web & Data Center) - Windows XP SP1 - Windows XP SP2 - Windows XP Home - Windows XP Media Center - Windows 2000 - Windows 98 Understanding The Boot Process timeline: - CD Shell lets you choose which XXXX.DAT file to load. XXXX.DAT is a boot sector located on the DVD root and there's one for each OS you want to load - The boot sector (PRO1.DAT for example) loads the SETUPLDR.BIN file located in each of the boot folders - SETUPLDR.BIN does a number of things and in turn loads txtsetup.sif which accesses the appropriate DVD\SETUP\XX folder and starts the text-mode setup for Windows - Once the text-mode setup of Windows is followed through the graphic-mode setup is started Timeline (countdown) T-39 - Depending on the boot folder, winnt.sif's DetachedProgram creates a "tag" file wich solo purpose is to tell Install.cmd wich OS is beeing installed T-13 - Svcpack.inf launches the RunOnce.cmd inside ...\i386\CMD\ of every OS wich purpose is to find Install.cmd on the DVD and execute it. This is due to DVD-drive letter changing. Mine can be D: yours can be H:, so the path is not allways the same. A search function is used. T-13 - Install.cmd checks for the tag file and then performs that OS's associated task, whether it beeing automaticly installing software, removing something from the HD or presenting a message. Before we start: Keep it simple, for boot menu use CD Shell, use simple winnt.sif files, etc. You should beautify, only after you'd successfully completed and booted from all OSs. Some beautifying options are at the end of this guide. What you will need: - Time and patience, don't expect to get everything to work the first time. Work on one operating system at a time. Test once you have that operating system added to make sure everything works right, then move onto the next OS. It will save you time if something goes wrong and you'll know where to look. You can only test your DVD once you've passed the "Creating the ISO" section. - Various operating system CDs or ISOs - Sufficient drive space (5+ GB to be safe) (I used +/- 20GB for my DVD) - CDImage (GUI'ed version) - Seems the link is not working, google it - CD Shell - Hex Workshop to hex-edit files. - Optional - VMware (Shareware), Virtual PC (Freeware) or Qemu (Freeware) (for testing purposes) - Any ISO burning software, like CDBurner XP (Freeware) Let's get started: Let's set up our folder structure: - In your C:\ (or whatever folder you choose to be the root folder) create this folder structure: ------------------------------------ DVD\BOOT\ DVD\SETUP\ ------------------------------------ DVD is the root folder and SETUP will store all of the CDs (DVD\SETUP\XP\Professional for example) - Extract the CD Shell.zip file and move the BOOT folder into the DVD folder (DVD\BOOT\) - Move the TOOLS folder into the BOOT folder (DVD\BOOT\TOOLS\) - Copy all the contents of the XP Pro CD to DVD\SETUP\XP\Professional. Automatically create multi-boot folders and files (thanks to geitonaki) - Download geitonaki's SFX file - Execute it and browse to your DVD folder. When finished it will open create_boot_folders.cmd, modify it to your needs. - It will create the PRO1 boot folder, modify setupldr.bin, modify txtsetup.sif, create the PRO1.bin boot sector and copy the WIN51, WIN51IP and WIN51IP.SP1 (WIN51IP.SP2 if Service Pack 2) tag files. (Notice that PRO1.bin has to have exactly 4 letters UPPERCASE) call create_boot_folder.cmd C:\DVD\SETUP\XP\Professional C:\DVD PRO1 FOO 0- Create a text file, inside PRO1, with NotePad, and rename it to winnt.sif. This will make winnt.sif create a "tag" file that identifies the OS being installed. In this case, the tag file will be XPPRO.TAG, but you can specify whatever you want. Creating RunOnce.cmd - Create a RunOnce.cmd file inside DVD\SETUP\XP\Professional\i386\CMD\ and paste the code in. - RunOnce.cmd looks for Install.cmd on the DVD and calls it. You can use the RunOnceEx method for this. RunOnceEx only runs at first logon, so applications may need reboot. The method above goes around that, it's "rebootless" Launching RunOnce.cmd from Svcpack.inf - Add these lines to svcpack.inf inside DVD\SETUP\XP\Professional\i386\: Notes: - Svcpack.inf may come as svcpack.in_, just use the eXPander utility (thread here) to extract the svcpack.inf inside it, then delete the svcpack.in_. - As you can see Svcpack.inf will launch RunOnce.cmd at T-13 stage. - You'll have to addapt the [ProductCatalogsToInstall] in svcpack.inf according to the new CatalogSubDir="\i386" because it may point to a different location (in which case you'll get an error message during installation). If you don't have any file references under [ProductCatalogsToInstall], then just don't worry about it. - Use the eXPander utility to transform svcpack.inf back to it's compressed svcpack.in_ form, which is smaller (this is optional). Creating the Install.cmd file - Create a Install.cmd file inside DVD\SOFTWARE\ and paste in the following: Install.cmd checks for any tag file and when it finds performs the associated task. As you can see, aplications are installed directly from the DVD (not copied to the HD) thus not needing the OEMPreInstall=Yes or [GuiRunOnce] in winnt.sif, that you can still use to launch some more stuff that you may need, and saving time Finishing Up DVD Layout: Ok, now check if your DVD layout is similar to this, if it is, everything is ok. Keep in mind that this is just a sample layout. This layout includes XP Pro and Server 2003, but you may add as many as you like or as many as it fit's on the DVD C:\DVD\ - Multi boot DVD Source C:\DVD\BOOT\ - CDShell folder C:\DVD\i386\ - Windows XP Pro reduced source folder (OPTIONAL) C:\DVD\PRO1\ - Boot folder 1 for XP Pro C:\DVD\PRO2\ - Boot folder 2 for XP Pro C:\DVD\3ST1\ - Boot folder 1 for Server 2003 C:\DVD\3ST2\ - Boot folder 2 for Server 2003 C:\DVD\SOFTWARE\SOFTWARE\ - Folder where software is placed C:\DVD\SOFTWARE\Install.cmd - CMD file that takes care of the software installation C:\DVD\SOFTWARE\SOFTWARE_ALL\ - Folder where software for all OSs is placed C:\DVD\SETUP\XP\Professional\i386\CMD\RunOnce.cmd C:\DVD\SETUP\Server2003\Standard\I386\CMD\RunOnce.cmd Creating a boot menu (CDShell): It's time to create a boot menu. CD Shell scripting it very simple and I believe that if you read my example you'll find it very easy to modify to your needs. Creating the ISO (CDImage): Now we only need to create the ISO so we can test our DVD. I'll follow the non-GUI CDImage tutorial, but you can use the GUI'ed CDImage version if you like. Put the cdimage.exe in the same directory as the DVD: ------------------------------------- C:\CDImage.exe C:\DVD ------------------------------------- And automate the process: Make a batch file that you can run whenever you want to make the ISO. To create a batch file open Notepad and paste the below code into it. Save the file as whatever you want and then just change the extension to .bat, like C:\makeiso.bat. Ok, now everytime you execute makeiso.bat it will create the ISO for you. It's time to test your ISO (with VMware for example) and add another OS! Extras Add an Unattended option: This section will teach you how to add an option which let's you install Windows unattendedly. - Copy the PRO1 folder and PRO1.DAT file to "Copy of PRO1" and "Copy of PRO1.DAT" - Rename it to PRO2 and PRO2.DAT - Hex-edit PRO2.dat and scroll down until you see "PRO1" in the right hand side. Replace PRO1 with PRO2. - Hex-edit setupldr.bin inside the PRO1 folder and Ctrl+H, then search for Type: "Text String" "PRO1" and replace it with PRO2. - Save the file, choose not to back it up. - Click "OK" and then choose "Replace All". It should say "4 Occurrences Replaced". When done, save the file and choose not to back it up. - Edit winnt.sif to include the unattended options. This may be a good time to read the ref.chm file in Microsoft Deployment Tools, it explains how to set up winnt.sif for an unattended installation. You can use your winnt.sif file to skip some boorings steps of your installation like typing the serial number, defining your language and keyboard or even skip all the steps with the UnattendMode=FullUnattended command. After you created your winnt.sif add these lines to it, so it TAG's the OS being installed: - Ok, so now we have a second boot option. Its time to add that option to the boot menu, so you can actually choose it. Just open up your DVD\BOOT\cdshell.ini and add these lines to it: Add Windows 98 Follow this guide, by chon_. Add Drivers: Follow this guide, by a06lp. Additional Resources - Setup Billboard Screens (or learn how to make your own here). - Microsoft Deployment Tools at Microsoft and Rapidshare. They contain the ref.chm file that has info for WINNT.SIF configuration, along with other utilities. And that's it, i'll be updating as i can Hope it was usefull to you cdshell.ini
  12. Wow, that is awesome! I'll use it along with my multi boot DVD in Media Center Thanks m8!
  13. Hi T D! Thanks for your answer but i don't want to use the $OEM$ folders. I just love my configuration, it's extremly easy to maintain or update plus gives me some more cool features applyable to multi boot CD/DVDs. Anyone knows what is needed for svcpack.inf to execute files? Please...
  14. Yes, Server 2003 has a better kernel and new security features, thus making Server 2003 better than XP in everything. Of course that if we are going to compare them we must do it in raw installations, with no software installed at all, no modifications or regtweaks. Conclusio? Server 2003 is better
  15. Lololol! Exactly... You forgot a measly line It happens Cya!
  16. Hi there! I don't understand what you mean, you want to disable a folder structure? How do you disable any structure at all? Do you mean disable Windows relation to those folders? Explain a little bit more your point of view please.
  17. First of all, thank you for your answer slatz! What you say is right for some installations, but not this one, because the only function of CleanUp.cmd is to apply Registry Tweaks and delete some files that exist inside %SystemRoot%. Besides the installation SFX's are inside the DVD, thus not able to be deleted I'll explain the working way of my DVD a little bit more: T-40 - txtsetup.sif copys Tweaks.reg to %SystemRoot% Tweaks.reg is cabbed into TWEAKS.RE_ T-39 - Winnt.sif's DetachedProgram creates a tag file named "SOFTWARE.TAG" in %SystemDrive%. Every boot folder has it's own winnt.sif. If i want to unattendedly install software I call the correspondent boot folder with the DetachedProgram feature in the winnt.sif file, so it creates the ta file (SOFTWARE.TAG). If I don't want to unattendedly install software I call another boot folder that doesn't have the DetachedProgram featura in winnt.sif. T-13 - Svcpack.inf installs obligatory software and launches RunOnce.cmd & CleanUp.cmd Svcpack.inf launches SFX's that just add/overwrite themes, cursors and user account pictures (UAP.exe) and installs XPize v4.3. Then launches RunOnce.cmd & CleanUp.cmd 1 - RunOnce.cmd calls the Install.cmd (which is inside the DVD at %CDROM%\Software\ and is the same for every OS).2 - CleanUp.cmd & Install.cmd are launched at the same time. 3 - Install.cmd checks for the tag file SOFTWARE.TAG as if exists installs the extra software it was mean to install. Then deletes some unnecessary files generated by the installations. 4 - CleanUp.cmd copys the CD Source files to %SystemRoot%\Source\, applys Tweaks.reg and finally deletes some unnecessary files inside %SystemRoot%, like BMP's. As you can see, aplications are installed from the DVD, not copied to the HD, thus not needing the OEMPreInstall=Yes. EDIT: Updated the 1st post so people can understand my problem more easily. André Casal
  18. Hi there! I have a multi boot DVD with several boot folders for each OS. The thing is that svcpakc.inf doesn't seem to launch any of its files... My original svcpack.inf: My fixed svcpack.inf: See the diference? That little "\" in CatalogSubDir="\i386" made all the diference. If anyone has this problem here's the solution. This bugged me for quite a long time... But now is solved! Cya
  19. Yeph, on more vote to Winnt.sif's "OemPreInstall = Yes", you probably have set it to "No". Good luck André Casal
  20. Hi there! Ok, afaik it could be your FINDCD.EXE. Try reading flyakite's tutorial again more carefully to see if you did everything right. If the problem persists try using a diferent 98SE.IMG. You have to use WinImage to convert from *.EXE to *.IMG. André Casal
  21. Pros and Cons i don't know, but i can tell you that i just finished reading a review in http://www.baboo.com.br/ that effectively compares XP Pro SP1 with Server 2003 Enterprise and Server 2003 wins in all benchmarks. Graphics, memory, HD, etc... André Casal
  22. Yeph, CD1 is Windows Server 2003 SP1 and CD2 is just the R2 Components. And if you copy the CD2 root into CD1, R2 components slipstream during instalation and the CD1 size stays under 700MB. This way you can have only one CD that installs Server 2003 SP1 with R2 components allready slipstreamed Good luck André Casal


×
×
  • Create New...