Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Saint Lucia

Everything posted by JPamplin

  1. Yes, I had the exact same problem. I think it complained about a variable in the config.ini not being declared (this was using install.exe in my unattended build - running install.exe manually works fine. It was this one: ;(Y)es for All Users or (N)o for only this user $OP_1= "Y" I also tried to replace the version of aaw2007.exe with the latest ( from download.com - this file was placed in \setup - would that make any difference? Thanks for a great tool! JP
  2. D, Thanks so much for getting back to me on this. I'm a little embarassed, because we've been discussing two different features. You've been talking about the search bar on the taskbar, and I've been referring to the Web icon in the main interface (which I don't want to see - just the rest of them). Sorry for the mixup - any ideas on getting rid of Web? Thanks, JP
  3. Halfwalker: Thanks so much for the tip! I had a bit of trouble with it, though, and I was wondering if I could get your input: 1) The first key you provided is almost correct, but Windows doesn't allow registry branches in HKEY_USERS like SOFTWARE - it has to be the user code of .DEFAULT, or the long string of numbers which identifies the user. In my case, the first key should be: [HKEY_USERS\S-1-5-21-109903746-2060566131-3148740645-1218\Software\Copernic\DesktopSearch\Meta] "InstalledComponents"=dword:0000009d 2) If you are entering the key manually, should it be hexidecimal or decimal? I can't make the capital D stick with hex. 3) I haven't tried this with a clean setup, but should this be applied right after the first install of Copernic? I quit an existing install of 1.63, applied the patch, and restarted Copernic, and Web was still there. 4) Would this work with the .DEFAULT branch of HKEY_USERS, so that every user would get the patch? Thanks, sorry for the n00bie questions, JP
  4. OK, the /S switch does work, then you can apply a .reg file from a previous install to duplicate your preferences. Now, the question of the day: ever since 1.61 Copernic forces the Web Tab to be visible. Has anyone figured out how to turn it off? Inquiring minds want to know, TIA, JP
  5. That's exactly the style of installation I have done for about 2 years (not a restore partition, but an "install from scratch" setup from D: to C:). Do a post search on username "JPamplin" and you'll find some posts I have done on the subject. I would be happy to post some of my script files now that the process is fairly stable and tested. Good luck, JP
  6. Guys, I would completely ignore the subtleties of trying to do this with a SIF file and just boot into DOS and run a batch file to reformat your drives. If you just have a C: drive, then checking for the existence of a D: will always be false, so use AEFDisk or other free DOS utility to programmatically reformat the drive as a C: and D: and reboot. If D: DOES exist, then the check is TRUE and you can launch your install script. I have outlined all the code you need to accomplish this in a previous post: http://www.msfn.org/board/index.php?showtopic=31871&hl= You may want to play with my routine a little bit - here's how: change the check routine to copy a little text file to the D: drive, then check for the existence of that file. If the D: drive exists, then the file will copy without error, but if D: does NOT exist, then the file won't be there. That might be a better way to check for the existence of d:. I haven't played with it lately so I don't know, but I can try to create a better check routine if people ask for it. JP
  7. I was thinking of including Konfabulator in my standard build, but I am a bit distressed at it's RAM usage. I had tried out several widgets and the total RAM usage was about 100MB! Anyone know if that will be remedied later? JP
  8. Make sure, if you are starting from DOS, that you use SMARTDRV disk caching with 2MB of cache for the C: drive and the CDROM drive. It makes stage 1 (copying files in DOS) significantly faster. I also agree with copying all files to the hard disk BEFORE you run WINNT (the XP setup application in DOS). I copy all XP files, addons, apps, etc. to a D: partition in DOS before a single install takes place. It really helps speed. Here's how you set SMARTDRV up: 1. Get or create a Windows 98/ME DOS startup disk. 2. Find SMARTDRV.EXE that matches the version of DOS that's on the disk. In other words, if you have a Windows 98 DOS disk (my faviorite), then find the version of SMARTDRV that Win98 came with. 3. Copy SMARTDRV to your floppy, let's assume a:\ 4. In the floppy's AUTOEXEC.BAT file, add this: smartdrv.exe C+ D+ /V 2048 2048 This will set up SMARTDRV to setup a 2MB cache and apply it to C and D (assuming your hard disk is C: and your CD is D: - you can add as many letters as you have drives that can be seen in DOS). JP
  9. Here's an article I wrote about the command: http://www.msfn.org/board/index.php?showtopic=26296&hl= This applies to installing network printers on a local machine, assuming you have added the IP ports via registry file beforehand, then stopped and restarted the Print Spooler service programmatically. I can post complete code if you need it. JP
  10. Genex, OK, first of all, you can name your WINNT.SIF file anything you like, and place it anywhere you like, as long as both the filename and path are stated as parameters when you call WINNT (at least this works out of DOS): ECHO. ECHO Starting Windows XP Setup... ECHO. @d:\Install\WinXP\i386\winnt /s:d:\Install\WinXP\i386 /u:d:\batfiles\XPAPPS.sif As you can see from one of my scripts above, I renamed WINNT.SIF and placed it in a custom folder, which is called in the /u: parameter, and seperately, named the path to the install files with the /s: parameter. Secondly: if you wish to create your own WINNT.SIF file on the fly, it could be done in DOS prior to the calling of WINNT. Let's say, for instance, you wanted to specify the activation key for an install. You could use a DOS batch file to capture the key, then write it into a SIF file. I don't have the exact code on hand, but here how it could work, from a logic standpoint: 1. Split your WINNT.SIF file right at the point where your key is written (without the key itself) and save them as two different files SIF1.txt and SIF2.txt. 2. Call a batch file to ask for the user's key, with a small DOS utility to capture the input as a variable (I use INPUT.COM - do a search). 3. Use DOS command to write the first part, the key variable, and the second part into a SIF file, then call WINNT with the path to the SIF file. Good luck, JP
  11. Bump again - I'm sorry but hopefully someone has run across this issue. If I don't get a response, I'll assume nobody knows how to do it. I'll update the thread if there's anything else I find out. JP
  12. Actual DOS, yes. Like Win98 Boot Disk DOS. How about it - have you created a DOS version?
  13. This is nice, but I need to do something like this in DOS. Any ideas? JP
  14. OK, Ryan, I see that the 5.0 Service Pack 2 package is on your site (http://www.ryanvm.net/msfn/). Any comments on changes in this release? Thanks, JP
  15. You can use the simple script for post-SP2 hotfixes I detail here: http://www.msfn.org/board/index.php?showtopic=39465&hl= JP
  16. Here's a registry tweak I developed to apply after silent install - it removes the Picasa Media Taskbar app: REGEDIT4 ;Delete NeroCheck, QTTask & WinAmp Agent from startup group [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "NeroFilterCheck"=- "QuickTime Task"=- "WinampAgent"=- "nwiz"=- "NvMediaCenter"=- "igfxtray"=- "SunJavaUpdateSched"=- "Picasa Media Detector"=- "DVDLauncher"=- I've got some other stuff in there too, but you can take out what you don't want. JP
  17. You just need to specify where the WINNT.SIF file is when you start WINNT. IT only reads it at the very beginning (you don't need to have the floppy in for the rest of the install cycle. I use the following: @d:\Install\WinXP\i386\winnt /s:d:\Install\WinXP\i386 /u:d:\batfiles\XPAPPS.sif Just put your path and filename after /u: and you'll be fine. JP
  18. This is a GREAT app, offered free by Copernic: http://www.copernic.com/en/products/deskto...arch/index.html I'd like to include it as a standard app in my unattended setups. Anyone play around with this and get a silent install working? If so, what switches did you use? Thanks, John
  19. Ryan, I use your Acrobat Reader 7, .NET Framework, Java Runtime 5.0 SP1, and (I think it's yours) WMP10 installers religiously! They are much appreciated. My goal, however, is to leave the WINXP SP2 folder absolutely pristine, and apply hotfixes and patches after the fact. That way, I don't have to re-RAR the entire 400MB WINXP folder every time there's a small change or hotfix, then upload that to multiple sites. I just need to figure out the correct command switches for everything, and modify my CMD file accordingly. Thanks for the quick reply, JP
  20. Hey there, I use the Filesystem=ConvertNTFS flag in my WINNT.SIF and it does a quick conversion of my FAT32 C: drive to NTFS during the install without wiping the volume. I do that manually first, and I have a D: FAT32 drive that all my installers are copied to beforehand. Is that what you're trying to accomplish? JP
  21. Hi folks, Well, it's that time again - time for me to make changes to my unattended CD, that is. If you've hung around MSFN for any length of time, you'll know me as the "Do Everything out of DOS" guy. My post-install script is not much different - I prefer a plain CMD script in GUIRunOnce rather than XPlosion Deelux 9.0 or whatever tools are out there. I like to leave my XP folder alone, and apply hotfixes after the base install. This is because I sync my install folder with several servers on our network, so that my assistants can use my scripts in other cities, and I want to upload as little data as possible. When I add a new hotfix, I just have to copy the KBxxxxxx.exe file and the new CMD script, and the folders are synced. Anyway, I have a section in my script for applying the post-SP2 hotfixes, as such (%A% is the path to my Apps folder): REM ******************** WINDOWS HOTFIXES ************************** ECHO. ECHO. ECHO Installing Windows XP Post-SP2 Hotfixes ECHO --------------------------------------- FOR %%H IN (KB867282 KB873333 KB873339 KB884020 KB885222 KB885250 KB885523 KB885626 KB885835 KB885836 KB885894 KB886185 KB886677 KB887078 KB887742 KB887797 KB888113 KB888240 KB888302 KB890047 KB890175 KB890830 KB890831 KB891781) DO ( ECHO. ECHO Installing %%H start /high /wait %A%\%%H.exe /q /n /z ) ECHO. ECHO. ECHO PART 2 - Non-Standard Installers ECHO -------------------------------- FOR %%K IN (KB831240) DO ( ECHO. ECHO Installing %%K start /high /wait %A%\%%K.exe /quiet /norestart ) For whatever reason, the following Hotfixes still show up as "needing to be installed" by Windows Update, after the whole thing is done: KB867282 - Cumulative Security Update for IE for XP KB886903 - Security Update for Microsoft .NET Framework 1.1 SP1 KB873333 - Security Update for Windows XP KB890047 - Security Update for Windows XP KB890830 - Windows Malicious Software Removal Tool - February 2005 I'm certain I have the hotfixes loaded and ready to install (except for 886903, which seems new), and they are installed during the post-XP GUIRunOnce script shown above - am I using the wrong command swtiches for a CMD window? Can anyone tell me the correct ones to use, or what to do about this? As always, thanks in advance. JP
  22. Spam spam spam spam spammity spammm! A useless post in a lost thread. Oh well. Hope everyone's doing well. ;-) JP
  23. http://www.msfn.org/board/index.php?showtopic=31871&hl= Read my posts towards the bottom. JP

  • Create New...