Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Electrician

  • Birthday 11/22/1954

Profile Information

  • OS
    XP Pro x86
  1. Do not see how it can be your runonceEx, since the reg entries do not run till system reboots - unless the problem is in syntax of reg add's (an error waiting for a reponse). I agree you should un-hide the process.
  2. Several ways, what method are you using to include foxit reader in your build? Are you "simply" copying the files over to the drive during windows install or are you running an installer (like in svcpack)? Also, do you want the reader to be a default for all users, or just there for the Admin logon? The path you ultimately want to effect (or is it affect?) is: "Documents and Settings\<users name>\Application Data\Microsoft\Internet Explorer\Quick Launch" With a shortcut in that location, that points back to the location of your exe. If this is ALWAYS the same (because you copied it there) you could create <and copy> a shortcut to the default user profile. You could also run an INF file during install that would create the shortcut for you. Which brings me to the final question; What ver of windows are you installing? 2k XP 2k3 vista???
  3. Check out the HFSLIP topic. You can build an installation CD that has all the updates and any custom settings you desire. El fantastico!!
  4. Do you mean an "In-place upgrade" ? You can do that by making a disk WITHOUT the Winnt.sif file. Choose install, then when it finds your current installation, choose repair option. If your CD has been slipstreamed with all the current updates (HFSLIP) then you won't loose a single update. This also keeps the programs (and reg entrys) which has gotten many of my friends out of a jam. If the sif file is on the CD you will never get the chance to do a repair install (in-place upgrade). You could keep the dif file on a floppy...
  5. Do you by chance have any other maps to that machine by it's name? Doing so, the system stores the name used during that connection, and will complain that the "information conflicts..." if you try to connect using a new name (your logon account assumed by default). Using the IP address instead is a known workaround to that problem. However, you didn't SAY that it was complaining in that way. I do not see how you can connect to an admin share with NO password via IP - unless it is accepting your logon by default and that logon is a local admin, as far as it is concerned . Do you have a local account on that machine? If so, and you are an admin (you should be since it is letting you attach at an Admin share) disconnect any other shares to that machine (including any in a script by "net use") and reboot. You can remap the all the shares by \\machine_name and should be golden.
  6. smilinjim I have never had messenger removed by integrating the USP's. I integrate them into my source (on disk) by doing this; "w2ksp51.exe /passive /n /integrate:E:\Create\W2ksp4_USP51" (for example) then IF I need to reduce size (often do), I use nlite for that. Of course, I also use HFslip to integrate all the current patches, etc. If you make a new CD, you can certainly do an in-place upgrade, which will add components and "restore" DLL's to the version on CD.
  7. Do not confuse Windows Messenger (the IM crapo) with the Messenger Service! You should see it listed under Services as "Messenger". That is what the program wants. Not as big a risk - but it was being MIS-used by web sites and spammers to throw pop-up messages at people. Messenger has not gone missing from any USP build that I know of. (Now, nlited on the other hand....)
  8. I agree with -I-, that this would best be "continued" as a rollup to Gurgelemeyers work. But don't count him out - he has been (IS?) ill and, God willing, will get better.
  9. $10 - ? At least they could make an upgrade version that was $99, if they REALLY want people to migrate from W2k to XP. Hey, remember how M$ claimed they could sell Office for $99 AND THEY WEREN'T DUMPING? Odd how, once they drove WordPerfect and other competitors out of business, it SUDDENLY got more expensive to make Office versions! The REAL reason they need to check IP/GUID/Lic# is to look for the users of Corp Lic ver's of XP. Keeping track of how many and what IP tells them if it is spreading...(IMHO). XP at work is ok, but there is LITTLE reason to compell me to upgrade my home machine from 2K, just as there is little reason to upgrade Office 97. Does what I need and the rest is B L O A T.
  10. I have done it successfully on several occasions - just make sure the CD you make does NOT have a winnt.sif file, or you won't be able to do the in-place upgrade. The CD restores all system files to the ver's on the CD, so add-ons that have replaced them will get "restored" aka; MP10 will not work - just re-install the tweaks from the svcp[ack.inf
  11. Actually it ships as part of the Windows 2000 Support Tools on the CD. Is there really anybody doing "this stuff" that DOESN'T add to their build?? Still, if you can work around it - great!
  12. I tried to Nlite an Nlited source and ttried to slipstream from an Nlited source - they both failed to make anything useable. Never tried to USP an Nlited source. As for changing shells.. example: single user change [HKEY_CURRENT_USER\Software\WinShellEx] "Default"="GeoShell" [HKEY_CURRENT_USER\Software\WinShellEx\GeoShell] "Start"="c:\\geotest\\GeoShell.exe" For all users: [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon] "Shell"="LiteStep.exe" [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon] "Shell"="c:\\litestep\\LiteStep.exe" etc etc. exact steps will be explained in docs for your new shell.
  13. Electrician


    My prev comment was not meant to accuse... I don't think it is illegal to hack files on your system, tho they may have an argument that to do so, requires some level of reverse engineering. As long as you don't share M$ components... And, yes, I don't think they would harass msfn folk because we are being "enthusiasts". Still, don't kick a giant. @squeeto ref to Star Wars - Jedi mind trick used to get past Empire solders.
  14. Are you using a SATA (or scsi) drive, and did you use F6 to install drivers for same?
  • Create New...