Jump to content

rtK

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Spain

Everything posted by rtK

  1. XP can deal with large FAT32 partitions with no problems.Except by design since win2k ms limited their tools to not to create fat32 partitions larger than 32GB forcing the users to use NTFS on larger volumes which is much more reliable. I'd say that your hdd is damaged. Backup the data and try to zerofill repartition and format the hdd , it will either fix the drive or kill it
  2. I would run a scan looking for spyware and similar crap. Id say it some nasty "add-on" trying to call home.
  3. The best way to have both is to build a multiboot dvd. follow this guide
  4. It should look Asin says. Without the commas the %systemdrive% var won't be translated into its real path.
  5. Hmm looks like you you are putting some wrong paths this is a part of the script I use to make unattended installs over network with PE (I use MS PE not Bart's) @echo off set installroot=..\os\es_pro set SetupFiles=%installroot%\i386 set AnswerFile=..\os\sif\prooem.txt %SetupFiles%\winnt32 /syspart:c: /tempdrive:c /s:%SetupFiles% /unattend:%AnswerFile% /makelocalsource /copysource:lang This baby been working like a charm since final xp was out
  6. AFAIK VLK OFFICE 2003 dont have any activation button on the toolbar
  7. Hmm I tried using live hdd install of pe for making my images but I had lots of problems with it , now im using a script to rebuild everything as needed ie when I update or add a driver or two it takes about 5 mins to rebuild my pe with all the drivers and tweaks ( tools , .Net support , etc) I find clean builds to work much better than tweaked old installs with overwritten files and broken infs PE can be a lifesaver or a big pain in the rear , and you know it EDIT: I wouldn't use ghost for something as volatile as PE is Each time I sit down and try and tweak my PE I rewrite half of the scripts lol.
  8. Why don't you hardcode the path? In XP registry Shell Folders paths are hardcoded. "X:\path\to\your\desktop" should work fine.
  9. Just a small addition: I've been using wpi over network for some time, the method is simple , a cmd script similar to athomsen's which maps network drive and calls wpi.hta. A small tweak was added to generate.js , that is we change drive type constant to that of network drives (3). wpiscripts/generate.js function GetCDRomDriveLetters() { position = "generate.js"; var li, en; li = new Array(); en = new Enumerator(fso.Drives); for (; !en.atEnd(); en.moveNext()) { ite = en.item(); if (ite.DriveType == 3) { li[li.length++]=(ite.DriveLetter + ":"); } } return li; }
×
×
  • Create New...