Jump to content

Dynamite

Member
  • Posts

    27
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by Dynamite

  1. Thanks Kelsenellenelvian Just the job, I'm moving from batch file method to WPI and was looking for a way of starting WPI after Windows has fully installed instead of at T12/T13 so I'll give your RunWPI.cmd a go - Thanks again
  2. I'm a newcomer to WPI but don't really see any need for music at this stage. It can wait IMHO until all is installed and running smoothly.
  3. Hi, Just a thought. As an alternative way to the same ends, you could build no start-up/shutdown sounds into a custom theme. This way you can modify all your sounds if you wish
  4. OK joshiieeii I'll give that a go Edit Trouble is Nlite seems to need NTFS and I'm on FAT32 (for backup reasons)
  5. I have XP Pro (original with no service packs) this CD can see my RAID array I Have slipstreamed SP2 into the above as per the guides. this CD cannot see my RAID array, it states there are no hard drives detected I have also tried putting updated Highpoint RAID drivers into my slip'ed CD but still no joy. Slip'ed CD works fine if installing onto a single HDD, but not RAID 0 Question is: What am I missing? I recently downloaded a Slipstreamed DVD made by somebody else, to see if it was just my CD's and this works fine. But has a different file structure (no extra drivers) System: Abit KT7A RAID AMD Athlon 1.2GHz IBM 40GB HDD's (now Weston Digital 80GB HDD's) First part of my winnt.sif - including drivers [Data] AutoPartition=0 MsDosInitiated = 0 UnattendedInstall = Yes [Unattended] UnattendMode = FullUnattended UnattendSwitch = Yes OemPreinstall = Yes OemSkipEula = Yes ComputerType = "Advanced Configuration and Power Interface (ACPI) PC", Retail FileSystem = * WaitForReboot = No TargetPath = "\Windows" DriverSigningPolicy = Ignore NonDriverSigningPolicy = Ignore OemPnPDriversPath="Drivers\006_storage;Drivers\006_storage\3ware;Drivers\006_storage\3ware\6000;Drivers\006_storage\3ware\7k&8k;Drivers\006_storage\acard;Drivers\006_storage\acard\6280;Drivers\006_storage\acard\6290;Drivers\006_storage\acard\67160;Drivers\006_storage\acard\671x;Drivers\006_storage\acard\6880;Drivers\006_storage\acard\6890;Drivers\006_storage\acard\68x5;Drivers\006_storage\adaptec;Drivers\006_storage\adaptec\aac;Drivers\006_storage\adaptec\aar1210;Drivers\006_storage\adaptec\i2o;Drivers\006_storage\adaptec\u160;Drivers\006_storage\adaptec\u320;Drivers\006_storage\adaptec\u320r;Drivers\006_storage\ali;Drivers\006_storage\amd;Drivers\006_storage\highpoint;Drivers\006_storage\highpoint\hpt366;Drivers\006_storage\highpoint\hpt371;Drivers\006_storage\highpoint\hpt374;Drivers\006_storage\highpoint\hpt3xx;Drivers\006_storage\highpoint\rr182x;Drivers\006_storage\intel;Drivers\006_storage\intel\eide;Drivers\006_storage\intel\sataraid;Drivers\006_storage\intel\u320r;Drivers\006_storage\ite;Drivers\006_storage\lsilogic;Drivers\006_storage\lsilogic\megaide;Drivers\006_storage\lsilogic\mraid35x;Drivers\006_storage\lsilogic\mylex;Drivers\006_storage\lsilogic\symmpi;Drivers\006_storage\nvidia;Drivers\006_storage\nvidia\eide;Drivers\006_storage\nvidia\raid;Drivers\006_storage\promise;Drivers\006_storage\promise\fasttrak;Drivers\006_storage\promise\fasttx2k;Drivers\006_storage\promise\sx4000;Drivers\006_storage\promise\sx6000;Drivers\006_storage\promise\ulsata;Drivers\006_storage\promise\ultra;Drivers\006_storage\qlogic;Drivers\006_storage\qlogic\12160;Drivers\006_storage\siimage;Drivers\006_storage\siimage\3112;Drivers\006_storage\siimage\3112r;Drivers\006_storage\siimage\3114;Drivers\006_storage\siimage\3114r;Drivers\006_storage\siimage\3124;Drivers\006_storage\siimage\3124r;Drivers\006_storage\siimage\649r;Drivers\006_storage\siimage\680;Drivers\006_storage\siimage\680r;Drivers\006_storage\sis;Drivers\006_storage\sis\eide;Drivers\006_storage\sis\raid;Drivers\006_storage\via;Drivers\006_storage\via\eide;Drivers\006_storage\via\ideraid;Drivers\006_storage\via\miniport;Drivers\006_storage\via\sataraid;Drivers\007_modem;Drivers\007_modem\Ambit;Drivers\007_modem\Ambit\Usbcm.inf;" Hibernation = No KeyboardLayout="United Kingdom"
  6. troycicle If you call your file 'config.xml' and put it into your ZoneAlarm folder [\$OEM$\$1\Install\Applications\ZoneAlarm]on your CD. It should pick this up duing installation, mine does.
  7. Yeh tcouto I got the same thing, with slipstreamed SP2 into the original XP. However I then used a CD with XP+SP1 (already slipstreamed) added SP2 and it works a treat. I have no idea why the black screen - couldn’t find anything on that at the time. Maybe it's stuck in a loop, maybe, I don't know. Sorry I can't be more positive, but your not alone.
  8. Yes - simple answer. I added SP2 to my XP/SP1 CD when SP2 first came out, as SP2 wouldn’t integrate successfully with my original XP. Always having problems during bootup. Since then I have tried again to slipstream SP2 into the original XP and had success. But it was BIGGER! than the XP/SP1 + SP2 (command line entry)strange but true
  9. I have it as December! strange I do have KB887742 as today though. Perhaps it's somesort of custom release thing from M$, just a thought
  10. I do a similar thing (I have UK only) which works fine, with no default US option showing [RegionalSettings] Language = 0809 also under [GuiUnattended] TimeZone = 85 also under [Unattended] KeyboardLayout="United Kingdom" I’m not familiar with the Kiwi keyboard layout but the time zone will of course be different
  11. Well my experence is, I put shortcuts in here... XPCD\$OEM$\$Docs\All Users\Desktop I also copy a little program called 'Desktop icon Layout' copied from my current setup, so that the layout is the same. Program can be obtained here [http://www.kellys-korner-xp.com/regs_edits/iconlayout.zip] and quick launch shortcuts are copied using a batch file, I find this method easier to keep track of. The shortcut is placed with it's program in the Install folder... Copy /y "%systemdrive%\Install\Applications\Winamp\Winamp.lnk" "%systemdrive%\Documents and Settings\Administrator\Application Data\Microsoft\Internet Explorer\Quick Launch\"
  12. Greg, try mounting your image onto a virtual drive with daemon tools and set the BIOS (press F2) to boot from this drive
  13. I'm afraid the '[PATH_to_config_file]\config.xml' doesn’t work for me, not perfectly anyway. It opens IE and SP2's popup blocker warning, but the config is set correctly, once I've closed IE manualy! anybody any ideas? Edit 06.11.2004 OK I've put the config.xml file inside the Zone alarm folder $OEM$\$1\Install\Applications\ZoneAlarm\ and it's picked up automatically
  14. Interesting reading this thread VigilanteLST As I experienced the same problems with no seaming cause. I even posted to the private microsoft newsgroups but nobody could solve (they did try) the problem. It's weird inst it everything slows to a crawl but nothing is using any resources. The moment I went back to SP1 all was fine again - put in SP2, all slow! - uninstall SP2 all fine again. A few others have had the same thing happen also. Time will tell, as always what the problem is.
  15. Yeh, you have a real problem there. Did you do a clean install, an upgrade from sp1 to sp2, use a slipstreamed CD? I don't think I'll be much help though, the same sort of thing happened to me. I got round it by formatting and starting from scratch. But when you get that screen in recovery console that ask's for a password and you don't have an admin password set just press enter By-the-bye when in recovery console your number keypad may not work, use the number along the top of your keyboard. Good luck, keep us posted haw your doing.
  16. I thought until recently the volume label that was put inside an .iso of an operating system was all important. Like WXPOEM_EN as one of mine is. But I've just made a slipstreamed XP-SP2 with the help of a program called nLite. It calls the volume 'WinLite' the iso 'WInLITE.ISO' It works fine. So what's all the fuss about? Does it matter to the installation what the volume is called/named?
  17. OK jimwillsher I’ve got one to work at last, in a round-about way. I used a copy of XP with slipstreamed SP1 in it as a starting point. (not the original XP disc) I then slipstreamed SP2 into this, using nLite with the help of this guide (by-the-bye it says you need to be on NTFS but I'm on FAT32 and it worked fine). I used nLite to make the ISO also. I've tested it on VMwares Virtual Machine and all appears fine. Some registry tweaks don't seem to work, but that’s probably because the location has been changed by SP2, just guessing at this stage. Anyways it boots, runs, shutsdown, restarts and programs run ok on it. I'll have to see how much junk can be removed before it stops working, but it's a start.
  18. I'm having the same problem [freezing during bootup] trying to load a slipstreamed XPSP2 onto a virtual PC. I can boot into safe mode ok, it waits quite a while during loading "mup.sys" but then moves on to the warning about going into safe mode. Can't get a newer BIOS (Abit KT7A RAID) for my machine or VPC! currently trying the upgrade method. update: No the upgrade method doesn't work either. The only way I have been able to get SP2 running successfully was to install XP from the original CD then run SP2 to update it, this works fine, but is a real pain! If anybody knows why the slipstreaming isn’t working properly please post!
  19. I'll give it a go, see what I can come up with. The only things that are replaced are those replaced by sp2. I have personaly removed nothing as yet. Still anythings worth a try Edit OK I've found some newer Highpoint drivers, with the help of the above guide, these have done the trick
  20. Hi, I have a pair of HDD's built onto a RAID 0 setup. (Abit KT7A Raid mobo) I have slipstreamed sp2 into my original XP pro. Trouble is when I boot from this CD in order to install it, my Raid drives cannot be *seen* by the slipstreamed CD. I also had the same trouble when I slipstreamed sp1. I've tried pressing F6 during setup and installing raid drivers from a floppy even though a message says something like 'we have controllers for this device' do you wish to continue yes/no. (tried both ways) The original XP pro does not have this problem and can *see* my raid array. The only way for me to install an up to date OS is to install the original XP and then apply the service pack to the installation. Very frustrating! My current (sp2) controller is hptxx.sys at 37.2KB Revision v1.0.5 (XPClient.010817-1148) One on original CD is hptxx.sys at 22.7KB I thought that replacing this with the controller from the original XP would cure this problem, but it doesn’t. I'm afraid I don't know much about drivers and how they work! Anybody got any ideas? by-the-bye the slipstreamed CD's can see my other stand alone HDD's
  21. I've read this, but have not tried it as yet... If you need to reinstall WindowsXP and want to keep all your current installed applications and settings: Start WindowsXP Go to the location of your source files Run WINNT32 /unattend It's always wise to backup precious items first of course
  22. There is a program about called 'NTFSDOS Professional' this apparently allows you to boot into an MS-DOS enviroment from a floppy and you can then edit or whatever, an NTFS drive just as if it were FAT/FAT32 Try a Google search good luck, let us know how you get on! from the ReadMe
  23. It would be really nice if threads were finished with a conclusion! Anyway hello all, nice site/forum you've got here. Is that required then for WINNT.sif Creator to work without error (0xc0000135)? .
×
×
  • Create New...