Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by skeebum

  1. Yes, it must be my configuration. I suppose there were some permission/ownership issues with the file or directory (.msi files are prone to being difficult when it comes to permissions) I moved the Setup.exe and Setup.msi files to the root of my systemdrive and it installed without a hitch. Maybe someone else owns my desktop... Thanks for the suggestion jcarle.
  2. Having trouble installing XPreview on XP SP2. Ran the installer for 1.0.6128 and it installed .NET Ran through the install but I receive the error Error reading from file C:\Documents and Settings\Z\Desktop\Setup.msi. Verify that the file exists and that you can access it. I can obviously access it since it is how I initiate the install. I have tried moving the file, downloading a different copy, initiating from Setup.exe, etc. Could you post an older version, perhaps the original 1.0 so that I have something to fall back on? I used the older version last year and it was wonderful. A bit rough around the edges ( what spawned updates it seems) but it got the job done. Excellent work jcarle!
  3. Elaborate on this "different way". I am still not sure of what you are asking.. perhaps my reading skills are lacking The more you elaborate on what your problem is, the more we can help you. Below is my configuration as an example. It has taken months to develop and perfect to my application. I followed his guide and I also have different configurations of a single OS which goes something like this... There are a lot of folders in the root of this CD but it all fits under 700MB. 3 versions of XP OEM Pro OEM Home VLK Pro CD Contents -OEM1 (SETUPLDR.BIN points to OEM_HOME, and contains winnt.sif) -OEM2 (points to OEM_HOME, NO winnt.sif) -... -OEM4 -PRO1 -PRO2 -... -PRO8 (each of the above folders have the files from the $WIN_NT$.~LS folder with modified SETUPLDR.BIN) -SETUP OEM_HOME --I386 OEM_HOME2 -- I386 OEM_PRO -- I386 OEM_PRO2 --I386 VLK_PRO --I386 VLK_PRO2 --I386 (The only reason there are the HOME2 and PRO2 folders is because of modified billboards) - Using CDIMAGE's -o optimize option so this fits all on a CD So essentially I have a CD that has 12 different configs of XP OEMPRO (Unattended, Attended, Billboards Unattended, Billboards Attended) OEMHOME (Unattended, Attended, Billboards Unattended, Billboards Attended) VLKPRO (Unattended, Attended, Billboards Unattended, Billboards Attended) for every install... - I use the SVCPACK method to install updates, copy program installs (optional, prompts user), and set wallpaper - RunOnceEx starts the silent installs
  4. I am having a hard time deciphering your post... It sounds like you have made a Multiboot cd with different installations of XP on it. Each one has a different folder the files are installing from, correct? Something like this... CD - SETUP -- I386 ----winnt.sif -- dflt ----winnt.sif -- norm Are you trying to make one version of the install be unattended and another be attended (allowing the user to select options)? Are you using a boot loader (ie CDSHELL) ? Give us a bit more info and we can help you further. Have you read flyakite's multiboot guide?
  5. Got it... Must have full path names to access the files on the CD Reference this post... http://www.msfn.org/board/index.php?s=&amp...st&p=523434
  6. I seem to remember having this problem some time ago, the error message you are seeing is from CDSHELL, I think. Do you even get a "Press any key to boot from CD..." prompt ? Try different media, make a simpler disk and progressively add more to it until it breaks, also try to get the exact error message and search for that. post it here too. Check your CDSHELL.ini too Try swapping DVD drives in different machines to isolate the drives.
  7. Flyakite's site has been moved to flyakite.msfnhosting.com
  8. skeebum

    Windows Path

    I think the only time that you could do that with an original CD is if you were installing to a partition that already contains an XP install, and you told it to install regardless, and if you go through the prompts correctly, and it is a full moon, it will prompt you for the install destination. Do you always clean install? Do you ever install from within windows? Also, if I am not mistaken, when you start the XP install from a DOS prompt using winnt.exe there was a command line option /d to specify the destination directory. It may be necessary to use /u, the unattended option, to activate /d. EDIT NOTE: I just checked for /d and it is no longer supported, sorry. It may also be possible to use the /t switch which copies the install files to a temp directory after which the installer prompts for a destination directory. I have not tried this before so my experience here is limited. As T D stated, you could use a winnt.sif answer file and specify the destination directory there but that would make your installation unattended (at least in part.) For more info, browse to your I386 directory on your CD from a command prompt and type " winnt.exe /? " (without quotes) FYI " winnt.exe /d /? " returns the unsupported option. Also: XP Deployment Tools Good luck
  9. Just some reference material for you Maelstorm... Ultimate Boot Disk Hiren's Boot CD This should give you a few ideas of what you could incorporate into your CD. Given enough room, or using a DVD you might be able to put the UBD on the same disk as your install. NOTE: I understand Hiren's boot disk contains "warez" or unlicensed, illegal software. It is only listed here for reference purposes.
  10. Thanks Siginet & 5128 ... I have been spending some time making that work these last few days. Its hard to concentrate on while putting out other fires but hopefully I will be able to test it today. Looks like a lot of work to make it copy properly since I have to combine some other batch files and streamline the whole system. Plus, it seems that I wont even be able to use OEMPreinstall for the unattended versions because each windows install shares the same I386 folder and svcpack.inf with its unattended counterpart (I also use the svcpack.inf method to install the 60something hotfixes.) Do you happen to recall which envvars do not work? Currently I am only using %systemdrive% Any info on this would save me some time since, to test properly, I have to install Windows to the T-12 mark and beyond.
  11. If you follow the directions on flyakite's tutorial for the ultimate boot cd i think you would find it similar to the method you would use to include the RescueMe cd.
  12. Thanks for the reply. The thing is, I don't want it to skip anything. It should be totally ATTENDED, as I need to be able to use the recovery console or do a repair install, or set domain settings during install, etc. I am currently using cmdlines.txt to call RunOnceEx.cmd to install the programs that are copied over. The RunOnceEx does execute, however it throws errors when trying to install because the $OEM$ folders didnt copy.
  13. I have been searching and experimenting with this topic for a few days now... I have a multiboot CD with 6 XP installs (2 OEMs and a VLK, each of which have unattended and attended setups) and all of them have $OEM$ folders Everything works as it should except for the Attended installs. I want to keep them attended to ensure that the recovery console or repair options could be used. However, I also want the $OEM$ folders to be copied to the drive when XP is installed. The only way I have attempted to copy them to drive is by using this Winnt.sif, however doing so skips the Recovery Console screen at the start of setup's execution and goes straight to the drive selection screen. I have experimented with different settings but as soon as I include the [unattended] tag, the install skips to the drive selection screen. [Data] AutoPartition=0 MsDosInitiated=”0” UnattendedInstall=”Yes” [Unattended] UnattendMode=ProvideDefault OemPreinstall=Yes OemSkipEula=No NoWaitAfterTextMode=1 NoWaitAfterGUIMode=1 WaitForReboot=”No” TargetPath=\WINDOWS DriverSigningPolicy=Ignore [GuiUnattended] OEMSkipWelcome = 1 Did I miss a setting in winnt.sif? Or should I go about this a different way? In summary, all I want to do is copy the $OEM$ folders to their respective locations on the drive while maintaining the Attended aspect of the install. Thanks for your help///
  14. Thank you for the in-depth reply. It would seem that Microsoft Update takes care of that concern. Forcing an automatic update resulted in the above mentioned update being displayed and updated, so you are correct in assuming that the Update site downloads the appropriate admin updates. A quick visit to the Office Update site showed no updates. The release of v6 could not have come at a better time.
  15. 80-something views but nobody cares to comment? This forum seems pretty dead to replies when compared with the unattended windows guide. It seems unlikely to me that nobody has encountered this before. The slipstream guide has been out for almost a year! If anyone has experienced this please respond to let me know. If I am all alone, at least I will know that I am doing something wrong. I read the post below by marek about slipstreaming SP1 + rebuild cd but there is still the use of administrative updates.
  16. Followed the Office 2003 SP1 + Hotfixes guide here. Excellent guide by the way. Used the disc I created a few times to install Office and it worked perfectly. No updates shown on Office update site. Now, two months after creating the slipstreamed cd, a single update appears at the update site. The only problem is that since administrative updates were integrated into the disc, the update site wont allow the update to download stating: NOTE: Detection shows that Office products on your computer have been updated by your Office product administrator from the administrative installation point on a server. This means that you should not update Office products yourself. If you are an Office product administrator, please visit the Office Resource Kit for more information. and... Update for Outlook 2003 Junk Email Filter (KB895658) You need the administrative version of this update due to previously installed administrative updates. Does anyone know how to get around this? I would like to have the end user be able to update office as necessary. Having scoured the web and the forums I havent found a solution to this problem. Hopefully this is an issue that has not been covered before.
  17. Is there a fast way to test whether the oobeinfo.ini file works the way I desire? Or am I doomed to reinstall Windows everytime I want to test a small change? I have read ref.chm regarding oobeinfo.ini but I do not see anything regarding how to hide certain pages from the user. Is it necessary to populate all the fields of oobeinfo to hide all the screens, except the User Creation screen (...the only one I want visible ?) I need a bit more info... EDIT: Discovered that there are numerous versions of ref.chm. The deployment tools cab I downloaded from microsoft ( KB838080 ) is newer than one I pulled from the CD (dated 2001). The one from the CD makes much more sense to me than the updated one. Even after reading the older ref.chm I am still unsure about what will hide or show pages. Anybody have an example of their oobeinfo.ini online somewhere? Maybe a small section could be appended to the unattended guide?
  18. I got the DirSize.dll to work but it always displays in bytes... short of learning to modify the source code, does anyone know how to fix this?

  • Create New...