Jump to content

Ghostrider

Member
  • Posts

    282
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

Posts posted by Ghostrider

  1. If your Dad is starting from scratch then I would recommend starting with a wireless (108Mbs) 4 port router, attach a 24port Gigabit switch, wire the place with Cat5e cable and install gigabit NICs in all computers, unless they come attached to the motherboards :P

    Now that you have setup the infrastructure you can connect your router to the server computer via a second 10/100 Nic, this i would have running W2K3 server for small business with exchange server (not SBS, there is a difference in licensing, unless 25 users is enough) you can allow the router or server to act as dhcp, i use the router but it's your choice.

    Now i would setup exchange server to login to your ISP and downloads/upload emails and as your workstations are all XP (pro) you can login to the server and have it install Outlook 2K3 and configure shares etc. if at a later time you want to run your own SMTP server you just need to update exchange. :thumbup

  2. Have you tried the Sysprep utility in the deploy tools, if your OS is functional you can run it then change the M/B, XP should re-detect on restart, you will have to reneter the Product key and user info etc

  3. Troubles getting CleanUp.cmd running propperly

    Problem:

    I have tried to get my CleanUp.cmd running after my unattended windows,

    drivers and applications install.

    Somehow all works out fine, but the CleanUp.cmd does not do it' s job propperly.

    After a succesfull install of windows, drivers and applications, the CleanUp.cmd

    does not start.

    When I manually klick the *.cmd, all gets cleaned as it should.

    Tried several things, but nothing would make it run automatically.

    This may seem very strange but i had the same problem, so i experimented and moved the shutdown command from the beginning to near the end of the instruction list and it now works :crazy: and you only need a 60 sec timer, 3 mins is kinda long especially as the instruction will now be near the end, not at the beginning.

  4. I am having a similar problem tha others seem to be having. I am doing my first build and I went with an amd64 cpu and asus k8v-e deluxe mob and a rain0 setup. When trying to install winxp it won't recognize the raid setup in the f6 mode. Setup accepts the drivers but then says "there is no disc in this drive" I've tried different drivers but most of them end up showing some other kind of error. Does anyone have any advice? B)

    F6 doesn't work in unnattended mode, you should use Bashrats method to create a unnattended CD with drivers included, then f6 will not be required.

    Edit ..P.S through experience i have learned that it's not a good idea to create a boot OS on a raid, mirrored or otherwise, when they fail you lose data big time, unless you ghost the drive then it won't matter.

  5. THe Updater injects again all resources to the file and adds the new file size value in the registry. That way you are protected by Windows File Protection and Windows Update will recognize what hotfixes has been applied, keeping of course the XPize taste :D

    Thanks... eagerly awaiting the release date... :yes:

  6. Holy Cow.

    I thought that ver. 2.5 looked great, but ver. 3, ****.  :thumbup

    Hope that the release date isn't to far away.

    Keep up the good work XPero.

    I second and third that.. :-D. i have a question though, version 2.5 has an update facility, does that just update the icons in the file or does it replace the file itself, say after a critical update from MS, i ask for reasons of security, no point replacing new files with older version... :rolleyes:

  7. I have working partial unnattended XP OEM, Retail and Corp installs which are slipstreamed, then I use xpinstall to install apps, hotfixes etc and then runonceex for final apps, batch and hotfix installs. part of this final phase i use a batch cmd to ask if oem files are to be installed and if so by whom and on what date, however i cannot think how i can add a machine serial number to install into the oeminfo file during install. I have winnt.sif on the cd but i also have a floppy version i can input user info and cd key etc.

    Can anyone help me, my mind has gone blank.. :}

  8. n the multiboot environ' there is a folder for each install O/S so you have to move drivers from the i386 folder to the folder above i386 in each install
    ...with my alternative method you will only one $OEM$ folder thus it is very easy to maintain.

    I saw your version, not a bad way to go, i have to use CD's at the moment so method 2 is the easiest with the space i have.. :}

  9. I'm making a dvd... so lot's of room  But if I integrate the drivers with method 1, will I be able to remove them? (let's say Bashrat suddenly changes the way drivers are integrated due to some major bug...)
    I find method 2 best for that, just change the relevant compressed file, BartPe has a different method of integration see other post.
    you need to copy or move the files from the i386 to the professional folder and up one folder in all the other multiboot cd folders..

    What do you mean by that? In for example pro1 and pro2, I already have similar files to the ones in setup\xp\proffessional\i386... (115 files and a 'system32' folder).

    in the multiboot environ' there is a folder for each install O/S so you have to move drivers from the i386 folder to the folder above i386 in each install

    One last question: If I integrate some updates and/or RyanMV's update pack, do I need to re-create those pro1 and pro2 folders?

    i found that ryans pack did not work in the multiboot disks, something to do with the changes in txtsetup.sif

  10. Oh well, I restarted anyway... now have xp in three languages on it! But still hav'nt integrated the driverpacks yet. Wich is the best method? 1 or 2?

    if you have lots of room then 1 is best, but if like me you are trying to fit 2 OS's on one CD then 2 is best

  11. Hello,

    first, i created an unattended dvd (no multi) of xp pro SP2. Then i decided to create a multi-boot dvd... using the dvd I already had (not burnt yet)

    I added xp pro normal and unattended, UBCD and BartPE (based on the dvd I had). I used this guide. When I try to test it in virtual pc, I can start cdshell, but when I try to run bartpe or windows xp installation, I get an error: can't find aec6280.sys

    For UBCD, it gets better: "can't boot from cd/dvd drive"

    I did a search for aec6280 in my directories and it is in:

    setup/xp/professional/i386

    I then tried to copy the file to pro1 and pro2, and extract it in BPE1, but that didn't change anything...  :(

    edit: Is this because I based BartPE and the windows install on an already unattended dvd? I did do the cleanup part in the guide, and the unattended part also (actually, I read the whole guide :P

    in your example

    I did a search for aec6280 in my directories and it is in:

    setup/xp/professional/i386

    you need to copy or move the files from the i386 to the professional folder and up one folder in all the other multiboot cd folders..

  12. Use the hacked files and modpe and compress the and copy them to your cd.

    Version 2.5 has an installer with updater so i want to use it, it can also be uninstalled if required, the older manual way you can't... but thanks for the reply anyway

  13. I am using this in my Unattended install, i have tried to install using XPInstall and also from runonceex but i just get the request for language. i even added /s /n /LANG=ENG and tested the script in windows itself and it works silently, but when i run the unattended install it keeps asking for the **** language and wont install silently... any help please... ??

  14. WinCDman is notorious for creating non-working multi-boots!

    Its better to do it manually.

    In anycase, WinCDman does not *ACTUALLY* slip-stream IE6SP1 into win2k. It can only just merge windows Service Packs and hot-fixes. And its a good idea to not start thinking of multi-boot until one has everything else working fine. :P

    I don't wish to be argumentative but it does integrate IE6, Messenger, Directx and Media player, also hotfixes and SPacks. Of course you can ask it to create a single OS cd but i never had a failure of any multiboot cd i created with it, although i usually only do 2 per cd ie OEM Home/Pro and Retail Home/Pro XP and Win2k Oem/Retail i also integrate $oem$ programs, drivers and codecs i use the results everyday to repair and build new computers.

    Most including myself prefer doing it manually but i have found this to work very well for basic slipstream/integration but i have had great success in conjunction with other manual means too. B)

    You can only try it, if you don't like it, dont use it... same goes for all forum available software, guides etc...

  15. Mine came from a few different sources, when i was still in primary school in england i was very pale skinned and got the nickname "Ghost" as i got older i rode bikes and my favourite colour of bike was a silver grey/black, i got into CB radio and loved the Meatloaf album Bat out of Hell and there was a line in that about ghostriders etc etc... the rest is history, (about 27yrs) :P i used the handle on CB and kept it ever since

  16. Attach your sysoc.inf please. I'm betting that the Window Management program screws up the entry in sysoc.inf in there which sets the registry entries.

    Sorry about that delay, this is from the created ISO, i already expanded it..

    I noticed that the RVMUpPck.inf entry is in there under hotfixupdates..just to give some further info, i just used Nuhi's tool to slipstream and add your pack, then i used the windows management program tocreate the multiboot cd, again no additions in it either just select O/S's and create.!

    sysoc.inf

×
×
  • Create New...