Jump to content
Compatible Support Forums

ViperZ2000

Members
  • Content count

    60
  • Joined

  • Last visited

    Never

Everything posted by ViperZ2000

  1. ViperZ2000

    Monitoring network speed

    I use a Linksys WAP54G wireless router for my internet connection for about 10 PCs in my house. Is there any way that I can monitor the bandwidth coming in and out of this device? I don't see anywhere where it support SNMP so PRGT and MRTG are out of the question. Thanks!
  2. ViperZ2000

    SATA and can I boot? (I'm new)

    Also, if you determine from above that your RAID chip/card is bootable, you'll need to press F6 just after booting from your Windows 2000, XP, or Server CD when prompted. You'll then need to have the RAID drivers on a floppy disk which MUST be drive A: since Windows will probably NOT have your drivers built in. Make sure that when you put these drivers on the floppy that you keep the SAME directory structure as what is in the download package. Example: a:\txtsetup.oem (I can't remember for sure but this file has to be in the root of A: ) a:\raid\*.inf & *.sys --> Check out the txtsetup.oem to find out the directory structure. It's not to difficult. If you want them built in to the CD and are up for a little challenge, check out the Sept or Oct 2004 issue of Maximum PC. It has a nice article on slipstreaming SP2 for XP (I think it tells you slipstreaming...and this works the same for 2000) and also adding RAID drivers to the CD. If not, check out nLITE (google search for it). It's a utility that will slipstream service packs, drivers, hotfixes, and also remove unwanted junk from the CD. I hope this helps you out!
  3. ViperZ2000

    Pop Up Ads from NT Compatible

    Google Toolbar 2.0 and Meaya PopUp blocker. I have them both running and only hear the popup being blocked form this site. I agree with you guys, pop-ups are annoying but if you use these apps, you'll never notice 99% of them.
  4. Well, McAfee is more popular so if a virus creator is targeting an AV program, this one and Symantec would be it. I've personally seen AV programs attacked. Pre-virus attacks can stop an AV "service" and replace that service with another that loads a fake icon in the system tray. From there on, the system is unprotected and vunerable for any kind of takeover, such as trojans, etc. Trend is probably the least likely of the three to be stopped, so for that reason only, Trend Micro gets my vote.
  5. Are you referring to one PC, small group of machines, or an enterprise? If a single PC, as long as the defs are updated, it makes no real difference. If you prefer to see details of you AV client, McAfee and Symantec are both very detailed whereas Trend does not show a lot. Another downside of trend is their defintion scheme...numbers instead of version and date as symantec does it. It's much easer to comprehend a date than a definition version number. For small groups and even an enterprise, I would say that you would want to have different clients on your Servers than you do on your clients. This is just a precautionary measure. Maybe trend didn't catch it on the mail server and NAV/McAfee did on the PC side. Also, there are standardization issues which most corporations are dealing with. Yeah, one AV solution is nice for troubleshooting and familiarity, but being "double-protected" is far better. Just my $.02 worth.
  6. ViperZ2000

    Ghosting with XP corporate

    Originally posted by lelton: Quote: Hi Guys, How is XP corporate with being ghosted over somewhat dissimilar hardware ? Does it "correctly" redetect its new hardware and uninstall drivers for undetected hardware. Please assume that the SID's will be changed on each machine. Les Actually, NO, you do not have to have more than 2 images for EVERY SINGLE DESKTOP OR LAPTOP. (Tablets...probably yes, separate images). Let me explain. At my company, we have approximately 25 different IBM notebooks and about 15 different Compaq/HP desktop models. As of 6 weeks ago, I had 30+ images. I now have 2 and the work GREAT on every single notebook and desktop model that we have. I finally figured out how to get Sysprep to work properly and populate all of the mass storage drivers. It's pretty simple to do and I'll outline the basic steps below. 1.) Build your image on a low end desktop. Mine happened to be a Dell PIII 933 (yes, and it works on all HP/Compaq desktops too) 2.) Grab all the windows updates and drivers for that PC that you want applied to your image. Other drivers are installed automatically ... see below. 3.) Install and configure your standard apps (acrobat, winzip, office, etc) 4.) Use ghost to send your image up to the network as a backup. 5.) Place all the drivers on your image (c:\support\drivers\nic;video; etc)for all the other systems. 6.) Use Sysprep to populate all the mass storage drivers and reset some network settings (I have this free software and inf file so it's basically ready to go- just fill in your product key) 7.) Use ghost to create a "production" image and then try it out on some PCs. Believe me, this works great! The only few things to reconfigure is DNS entries (if any), power mgmt settings, xp system restore, and that's about it!. I used my base Desktop image to start my laptop image so it went pretty quick. IBM has a ton of junk to install so that was why I went wit 2 images instead of only 1. Do a search for Sysprep 2.0 or Windows XP Corp Deployment Tools. This has the exe for sysprep. Here's my file. Just modify the driver locations first then put it with the all the files from the XP corp deploy tools in C:\Sysprep and run Sysprep. Check the top two boxes and hit RESEAL. Ghost it up as in step #6 above and VIOLA! ******* ;SetupMgrTag [unattended] OemSkipEula=Yes InstallFilesPath=C:\sysprep\i386 UpdateInstalledDrivers=Yes OEMPnPDriversPath=support\drivers\ibm\Audio\audio1;support\drivers\ibm\Audio\audio2;support\drivers\ibm\bl uetooth\bluetooth1;support\drivers\ibm\chipset;support\drivers\ibm\modem\modem1;support\drivers\ibm\nic\3c om;support\drivers\ibm\nic\intelpro1000;support\drivers\ibm\pm;support\drivers\ibm\trackpoint;support\driv ers\ibm\trackpointunav;support\drivers\ibm\video\video1;support\drivers\ibm\video\video2;support\drivers\i bm\video\video3;support\drivers\ibm\wireless\ibmhighrate;support\drivers\ibm\wireless\intelpro2100;support \drivers\ibm\wireless\dualband-abg;support\drivers\compaq\d510-530\audio;support\drivers\compaq\d510-530\b roadcom;support\drivers\compaq\d510-530\chipset;\support\drivers\compaq\d510-530\ich4;support\drivers\comp aq\d510-530\intelpro1000;support\drivers\compaq\d510-530\usb2;support\drivers\compaq\d510-530\video [GuiUnattended] AdminPassword="xxxxxxx" EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1 [userData] ProductKey=XXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="PC User" OrgName="Your Company Name Here!" ComputerName=* [Display] BitsPerPel=16 Xresolution=1024 YResolution=768 Vrefresh=72 [TapiLocation] CountryCode=1 AreaCode=222 [setupMgr] ;DistFolder=C:\sysprep\i386 ;DistShare=windist [identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=yes [params.MS_TCPIP] DNSSuffixSearchOrder = [sysprep] BuildMassStorageSection=Yes [sysprepMassStorage] *pnp0a00=c:\windows\inf\machine.inf *pnp0a01=c:\windows\inf\machine.inf *pnp0a04=c:\windows\inf\machine.inf *pnp0a03=c:\windows\inf\machine.inf pci\cc_0604=c:\windows\inf\machine.inf pci\cc_0601=c:\windows\inf\machine.inf pci\cc_0602=c:\windows\inf\machine.inf pci\cc_0600=c:\windows\inf\machine.inf pci\cc_0500=c:\windows\inf\machine.inf root\ftdisk=c:\windows\inf\machine.inf root\swenum=c:\windows\inf\machine.inf root\update=c:\windows\inf\machine.inf root\dmio=c:\windows\inf\machine.inf lptenum\microsoftrawport958a=c:\windows\inf\machine.inf root\rdpdr=c:\windows\inf\machine.inf root\rdp_mou=c:\windows\inf\machine.inf root\rdp_kbd=c:\windows\inf\machine.inf *pnp0000=c:\windows\inf\machine.inf *pnp0001=c:\windows\inf\machine.inf *pnp0003=c:\windows\inf\machine.inf *pnp0004=c:\windows\inf\machine.inf *pnp0100=c:\windows\inf\machine.inf *pnp0101=c:\windows\inf\machine.inf *pnp0200=c:\windows\inf\machine.inf *pnp0201=c:\windows\inf\machine.inf *pnp0800=c:\windows\inf\machine.inf *pnp0b00=c:\windows\inf\machine.inf *pnp0a05=c:\windows\inf\machine.inf *pnp0a06=c:\windows\inf\machine.inf *pnp0c00=c:\windows\inf\machine.inf *pnp0c01=c:\windows\inf\machine.inf *pnp0c02=c:\windows\inf\machine.inf *pnp0c04=c:\windows\inf\machine.inf *pnp0c0b=c:\windows\inf\machine.inf *pnp0c0c=c:\windows\inf\machine.inf *pnp0c0d=c:\windows\inf\machine.inf *pnp0c0e=c:\windows\inf\machine.inf *pnp0c15=c:\windows\inf\machine.inf acpi\dockdevice=c:\windows\inf\machine.inf acpi\dockdevice&_sb_.pci_.oak_=c:\windows\inf\machine.inf acpi\dockdevice&_sb_.pci_.isa_.slce=c:\windows\inf\machine.inf acpi\fixedbutton=c:\windows\inf\machine.inf acpi\thermalzone=c:\windows\inf\machine.inf isapnp\readdataport=c:\windows\inf\machine.inf pci\ven_10aa&dev_0000=c:\windows\inf\machine.inf pci\ven_1025&dev_1435=c:\windows\inf\machine.inf pci\ven_10b9&dev_1445=c:\windows\inf\machine.inf pci\ven_10b9&dev_1489=c:\windows\inf\machine.inf pci\ven_10b9&dev_1449=c:\windows\inf\machine.inf pci\ven_10b9&dev_1533=c:\windows\inf\machine.inf pci\ven_10b9&dev_1451=c:\windows\inf\machine.inf pci\ven_10b9&dev_1521=c:\windows\inf\machine.inf pci\ven_10b9&dev_1621=c:\windows\inf\machine.inf pci\ven_10b9&dev_1647=c:\windows\inf\machine.inf pci\ven_10b9&dev_1651=c:\windows\inf\machine.inf pci\ven_10b9&dev_1523=c:\windows\inf\machine.inf pci\ven_10b9&dev_1531=c:\windows\inf\machine.inf pci\ven_10b9&dev_1541=c:\windows\inf\machine.inf pci\ven_10b9&dev_5243=c:\windows\inf\machine.inf pci\ven_10b9&dev_5247=c:\windows\inf\machine.inf pci\ven_10b9&dev_7101=c:\windows\inf\machine.inf pci\ven_1022&dev_7007=c:\windows\inf\machine.inf pci\ven_1022&dev_700d=c:\windows\inf\machine.inf pci\ven_1022&dev_700f=c:\windows\inf\machine.inf pci\ven_1022&dev_740b=c:\windows\inf\machine.inf pci\ven_1022&dev_7413=c:\windows\inf\machine.inf pci\ven_1022&dev_7443=c:\windows\inf\machine.inf pci\ven_0e11&dev_0001=c:\windows\inf\machine.inf pci\ven_0e11&dev_0002=c:\windows\inf\machine.inf pci\ven_0e11&dev_1000=c:\windows\inf\machine.inf pci\ven_0e11&dev_2000=c:\windows\inf\machine.inf pci\ven_0e11&dev_ae29=c:\windows\inf\machine.inf pci\ven_0e11&dev_ae2b=c:\windows\inf\machine.inf pci\ven_0e11&dev_a0f0=c:\windows\inf\machine.inf pci\ven_0e11&dev_a0f3=c:\windows\inf\machine.inf pci\ven_0e11&dev_a0f7=c:\windows\inf\machine.inf pci\ven_0e11&dev_ae2a=c:\windows\inf\machine.inf pci\ven_0e11&dev_ae31=c:\windows\inf\machine.inf pci\ven_0e11&dev_ae69=c:\windows\inf\machine.inf pci\ven_0e11&dev_ae6c&cc_0600=c:\windows\inf\machine.inf pci\ven_0e11&dev_ae6c&cc_0604=c:\windows\inf\machine.inf pci\ven_0e11&dev_ae6d=c:\windows\inf\machine.inf *cpqa0ef=c:\windows\inf\machine.inf *cpqae08=c:\windows\inf\machine.inf *cpqae30=c:\windows\inf\machine.inf *cpqae3b=c:\windows\inf\machine.inf *cpqae3c=c:\windows\inf\machine.inf *cpqae4a=c:\windows\inf\machine.inf *cpqae4b=c:\windows\inf\machine.inf *cpqae4c=c:\windows\inf\machine.inf *cpqae4d=c:\windows\inf\machine.inf *cpqae53=c:\windows\inf\machine.inf *cpqae54=c:\windows\inf\machine.inf *cpqae55=c:\windows\inf\machine.inf *cpqb05f=c:\windows\inf\machine.inf *cpqb118=c:\windows\inf\machine.inf *cpqb119=c:\windows\inf\machine.inf *cpqb11a=c:\windows\inf\machine.inf *cpqfa1b=c:\windows\inf\machine.inf pci\ven_1080&dev_0600=c:\windows\inf\machine.inf pci\ven_1078&dev_0000=c:\windows\inf\machine.inf pci\ven_1078&dev_0002=c:\windows\inf\machine.inf pci\ven_1011&dev_0001=c:\windows\inf\machine.inf pci\ven_1011&dev_0021=c:\windows\inf\machine.inf pci\ven_1011&dev_0022=c:\windows\inf\machine.inf pci\ven_1011&dev_0024=c:\windows\inf\machine.inf pci\ven_1011&dev_0025=c:\windows\inf\machine.inf pci\ven_1011&dev_0026=c:\windows\inf\machine.inf pci\ven_103c&dev_10c1=c:\windows\inf\machine.inf pci\ven_103c&dev_10ed=c:\windows\inf\machine.inf pci\ven_103c&dev_1219=c:\windows\inf\machine.inf pci\ven_103c&dev_121a=c:\windows\inf\machine.inf pci\ven_103c&dev_121b=c:\windows\inf\machine.inf pci\ven_103c&dev_121c=c:\windows\inf\machine.inf *hwpc209=c:\windows\inf\machine.inf pci\ven_1014&dev_000a=c:\windows\inf\machine.inf pci\ven_1014&dev_0017=c:\windows\inf\machine.inf pci\ven_1014&dev_0022&rev_00=c:\windows\inf\machine.inf pci\ven_1014&dev_0022=c:\windows\inf\machine.inf pci\ven_1014&dev_0095=c:\windows\inf\machine.inf *ibm006a=c:\windows\inf\machine.inf *int0800=c:\windows\inf\machine.inf pci\ven_8086&dev_0008=c:\windows\inf\machine.inf pci\ven_8086&dev_0482=c:\windows\inf\machine.inf pci\ven_8086&dev_0483=c:\windows\inf\machine.inf pci\ven_8086&dev_0484=c:\windows\inf\machine.inf pci\ven_8086&dev_0486=c:\windows\inf\machine.inf pci\ven_8086&dev_04a3&rev_00=c:\windows\inf\machine.inf pci\ven_8086&dev_04a3&rev_01=c:\windows\inf\machine.inf pci\ven_8086&dev_04a3&rev_02=c:\windows\inf\machine.inf pci\ven_8086&dev_04a3&rev_03=c:\windows\inf\machine.inf pci\ven_8086&dev_04a3=c:\windows\inf\machine.inf pci\ven_8086&dev_1130=c:\windows\inf\machine.inf pci\ven_8086&dev_1131=c:\windows\inf\machine.inf pci\ven_8086&dev_1161=c:\windows\inf\machine.inf pci\ven_8086&dev_1225=c:\windows\inf\machine.inf pci\ven_8086&dev_122d=c:\windows\inf\machine.inf pci\ven_8086&dev_122e=c:\windows\inf\machine.inf pci\ven_8086&dev_1234=c:\windows\inf\machine.inf pci\ven_8086&dev_1235=c:\windows\inf\machine.inf pci\ven_8086&dev_1237=c:\windows\inf\machine.inf pci\ven_8086&dev_123b=c:\windows\inf\machine.inf pci\ven_8086&dev_123c=c:\windows\inf\machine.inf pci\ven_8086&dev_123d=c:\windows\inf\machine.inf pci\ven_8086&dev_123f=c:\windows\inf\machine.inf pci\ven_8086&dev_124b=c:\windows\inf\machine.inf pci\ven_8086&dev_1250=c:\windows\inf\machine.inf pci\ven_8086&dev_1360=c:\windows\inf\machine.inf pci\ven_8086&dev_1361=c:\windows\inf\machine.inf pci\ven_8086&dev_1460=c:\windows\inf\machine.inf pci\ven_8086&dev_1461=c:\windows\inf\machine.inf pci\ven_8086&dev_1462=c:\windows\inf\machine.inf pci\ven_8086&dev_1a21=c:\windows\inf\machine.inf pci\ven_8086&dev_1a23=c:\windows\inf\machine.inf pci\ven_8086&dev_1a24=c:\windows\inf\machine.inf pci\ven_8086&dev_1a31=c:\windows\inf\machine.inf pci\ven_8086&dev_2410=c:\windows\inf\machine.inf pci\ven_8086&dev_2413=c:\windows\inf\machine.inf pci\ven_8086&dev_2418=c:\windows\inf\machine.inf pci\ven_8086&dev_2420=c:\windows\inf\machine.inf pci\ven_8086&dev_2423=c:\windows\inf\machine.inf pci\ven_8086&dev_2428=c:\windows\inf\machine.inf pci\ven_8086&dev_2440=c:\windows\inf\machine.inf pci\ven_8086&dev_2443=c:\windows\inf\machine.inf pci\ven_8086&dev_2448=c:\windows\inf\machine.inf pci\ven_8086&dev_244c=c:\windows\inf\machine.inf pci\ven_8086&dev_244e=c:\windows\inf\machine.inf pci\ven_8086&dev_2483=c:\windows\inf\machine.inf pci\ven_8086&dev_248c=c:\windows\inf\machine.inf pci\ven_8086&dev_2500=c:\windows\inf\machine.inf pci\ven_8086&dev_2501=c:\windows\inf\machine.inf pci\ven_8086&dev_250b=c:\windows\inf\machine.inf pci\ven_8086&dev_250f=c:\windows\inf\machine.inf pci\ven_8086&dev_2530=c:\windows\inf\machine.inf pci\ven_8086&dev_2531=c:\windows\inf\machine.inf pci\ven_8086&dev_2532=c:\windows\inf\machine.inf pci\ven_8086&dev_2533=c:\windows\inf\machine.inf pci\ven_8086&dev_2534=c:\windows\inf\machine.inf pci\ven_8086&dev_3575=c:\windows\inf\machine.inf pci\ven_8086&dev_3576=c:\windows\inf\machine.inf pci\ven_8086&dev_3578=c:\windows\inf\machine.inf pci\ven_8086&dev_1a30=c:\windows\inf\machine.inf pci\ven_8086&dev_7000=c:\windows\inf\machine.inf pci\ven_8086&dev_7030=c:\windows\inf\machine.inf pci\ven_8086&dev_7100=c:\windows\inf\machine.inf pci\ven_8086&dev_7110&cc_0680=c:\windows\inf\machine.inf pci\ven_8086&dev_7110&cc_0601=c:\windows\inf\machine.inf pci\ven_8086&dev_7110&rev_01&cc_0680=c:\windows\inf\machine.inf pci\ven_8086&dev_7110&rev_01&cc_0601=c:\windows\inf\machine.inf pci\ven_8086&dev_7113&rev_00=c:\windows\inf\machine.inf pci\ven_8086&dev_7113&rev_01=c:\windows\inf\machine.inf pci\ven_8086&dev_7113=c:\windows\inf\machine.inf pci\ven_8086&dev_7120=c:\windows\inf\machine.inf pci\ven_8086&dev_7122=c:\windows\inf\machine.inf pci\ven_8086&dev_7124=c:\windows\inf\machine.inf pci\ven_8086&dev_7180=c:\windows\inf\machine.inf pci\ven_8086&dev_7181=c:\windows\inf\machine.inf pci\ven_8086&dev_7190=c:\windows\inf\machine.inf pci\ven_8086&dev_7192=c:\windows\inf\machine.inf pci\ven_8086&dev_7191=c:\windows\inf\machine.inf pci\ven_8086&dev_7194=c:\windows\inf\machine.inf pci\ven_8086&dev_7198=c:\windows\inf\machine.inf pci\ven_8086&dev_719b=c:\windows\inf\machine.inf pci\ven_8086&dev_71a1=c:\windows\inf\machine.inf pci\ven_8086&dev_7600=c:\windows\inf\machine.inf pci\ven_8086&dev_7603=c:\windows\inf\machine.inf pci\ven_8086&dev_84c4=c:\windows\inf\machine.inf pci\ven_8086&dev_84c5=c:\windows\inf\machine.inf pci\ven_8086&dev_b152=c:\windows\inf\machine.inf pci\ven_8086&dev_b154=c:\windows\inf\machine.inf pci\ven_1042&dev_3000=c:\windows\inf\machine.inf pci\ven_1042&dev_3010=c:\windows\inf\machine.inf pci\ven_1066&dev_0001=c:\windows\inf\machine.inf pci\ven_1066&dev_8002=c:\windows\inf\machine.inf pci\ven_1066&dev_0002=c:\windows\inf\machine.inf pci\ven_100b&dev_0011=c:\windows\inf\machine.inf pci\ven_1033&dev_00a8&cc_0600=c:\windows\inf\machine.inf pci\ven_1033&dev_00a8&cc_0000=c:\windows\inf\machine.inf pci\ven_1033&dev_00a9&cc_0600=c:\windows\inf\machine.inf pci\ven_1033&dev_00aa&cc_0500=c:\windows\inf\machine.inf pci\ven_1033&dev_00ab&subsys_00ab1033=c:\windows\inf\machine.inf pci\ven_1033&dev_00ac&cc_0600=c:\windows\inf\machine.inf pci\ven_1033&dev_00ad&cc_0600=c:\windows\inf\machine.inf pci\ven_1033&dev_00ae&cc_0600=c:\windows\inf\machine.inf pci\ven_1033&dev_00af=c:\windows\inf\machine.inf pci\ven_1033&dev_00b0=c:\windows\inf\machine.inf pci\ven_1033&dev_00b1&cc_0600=c:\windows\inf\machine.inf pci\ven_1045&dev_c822=c:\windows\inf\machine.inf pci\ven_1045&dev_c832=c:\windows\inf\machine.inf pci\ven_1045&dev_c557=c:\windows\inf\machine.inf pci\ven_1045&dev_c558=c:\windows\inf\machine.inf pci\ven_1045&dev_c567=c:\windows\inf\machine.inf pci\ven_1045&dev_c568=c:\windows\inf\machine.inf pci\ven_1045&dev_c700=c:\windows\inf\machine.inf pci\ven_1045&dev_c701=c:\windows\inf\machine.inf pci\ven_1166&dev_0005&cc_0604=c:\windows\inf\machine.inf pci\ven_1166&dev_0005&cc_0600=c:\windows\inf\machine.inf pci\ven_1166&dev_0007=c:\windows\inf\machine.inf pci\ven_1166&dev_0008=c:\windows\inf\machine.inf pci\ven_1166&dev_0013=c:\windows\inf\machine.inf pci\ven_1166&dev_0009&cc_0604=c:\windows\inf\machine.inf pci\ven_1166&dev_0009&cc_0600=c:\windows\inf\machine.inf pci\ven_1166&dev_0014&cc_0600=c:\windows\inf\machine.inf pci\ven_1166&dev_0011&cc_0600=c:\windows\inf\machine.inf pci\ven_1166&dev_0012&cc_0600=c:\windows\inf\machine.inf pci\ven_1166&dev_0014&cc_0604=c:\windows\inf\machine.inf pci\ven_1166&dev_0015=c:\windows\inf\machine.inf pci\ven_1166&dev_0016&cc_0604=c:\windows\inf\machine.inf pci\ven_1166&dev_0016&cc_0600=c:\windows\inf\machine.inf pci\ven_1166&dev_0200=c:\windows\inf\machine.inf pci\ven_110a&dev_001d=c:\windows\inf\machine.inf pci\ven_1039&dev_0001=c:\windows\inf\machine.inf pci\ven_1039&dev_0008=c:\windows\inf\machine.inf pci\ven_1039&dev_0009=c:\windows\inf\machine.inf pci\ven_1039&dev_0406=c:\windows\inf\machine.inf pci\ven_1039&dev_0496=c:\windows\inf\machine.inf pci\ven1039&dev_0540=c:\windows\inf\machine.inf pci\ven_1039&dev_0630=c:\windows\inf\machine.inf pci\ven_1039&dev_0635=c:\windows\inf\machine.inf pci\ven_1039&dev_0730=c:\windows\inf\machine.inf pci\ven_1039&dev_0735=c:\windows\inf\machine.inf pci\ven_1039&dev_6001=c:\windows\inf\machine.inf pci\ven_1055&dev_9460=c:\windows\inf\machine.inf pci\ven_1055&dev_9463=c:\windows\inf\machine.inf pci\ven_104c&dev_ac20=c:\windows\inf\machine.inf pci\ven_1179&dev_0601=c:\windows\inf\machine.inf pci\ven_1179&dev_0618=c:\windows\inf\machine.inf pci\ven_1179&dev_0602=c:\windows\inf\machine.inf pci\ven_1179&dev_0611=c:\windows\inf\machine.inf pci\ven_1179&dev_0603=c:\windows\inf\machine.inf pci\ven_1179&dev_0604=c:\windows\inf\machine.inf pci\ven_1179&dev_0605=c:\windows\inf\machine.inf pci\ven_1179&dev_0609=c:\windows\inf\machine.inf pci\ven_1060&dev_8886=c:\windows\inf\machine.inf pci\ven_1060&dev_886a=c:\windows\inf\machine.inf pci\ven_1060&dev_e886=c:\windows\inf\machine.inf pci\ven_1060&dev_8881=c:\windows\inf\machine.inf pci\ven_1060&dev_0891=c:\windows\inf\machine.inf pci\ven_1060&dev_e881=c:\windows\inf\machine.inf pci\ven_1060&dev_e891=c:\windows\inf\machine.inf pci\ven_1106&dev_0305=c:\windows\inf\machine.inf pci\ven_1106&dev_0391=c:\windows\inf\machine.inf pci\ven_1106&dev_0501=c:\windows\inf\machine.inf pci\ven_1106&dev_0601=c:\windows\inf\machine.inf pci\ven_1106&dev_0605=c:\windows\inf\machine.inf pci\ven_1106&dev_0691=c:\windows\inf\machine.inf pci\ven_1106&dev_3091=c:\windows\inf\machine.inf pci\ven_1106&dev_3099=c:\windows\inf\machine.inf pci\ven_1106&dev_3101=c:\windows\inf\machine.inf pci\ven_1106&dev_3112=c:\windows\inf\machine.inf pci\ven_1106&dev_0505=c:\windows\inf\machine.inf pci\ven_1106&dev_0576=c:\windows\inf\machine.inf pci\ven_1107&dev_0576=c:\windows\inf\machine.inf pci\ven_1106&dev_0586=c:\windows\inf\machine.inf pci\ven_1106&dev_0596=c:\windows\inf\machine.inf pci\ven_1106&dev_0686=c:\windows\inf\machine.inf pci\ven_1106&dev_3074=c:\windows\inf\machine.inf pci\ven_1106&dev_3109=c:\windows\inf\machine.inf pci\ven_1106&dev_8231=c:\windows\inf\machine.inf pci\ven_1106&dev_0597=c:\windows\inf\machine.inf pci\ven_1106&dev_0598=c:\windows\inf\machine.inf pci\ven_1106&dev_3040=c:\windows\inf\machine.inf pci\ven_1106&dev_3050=c:\windows\inf\machine.inf pci\ven_1106&dev_3051=c:\windows\inf\machine.inf pci\ven_1106&dev_3057=c:\windows\inf\machine.inf pci\ven_1106&dev_8235=c:\windows\inf\machine.inf pci\ven_1106&dev_8305=c:\windows\inf\machine.inf pci\ven_1106&dev_8391=c:\windows\inf\machine.inf pci\ven_1106&dev_8598=c:\windows\inf\machine.inf pci\ven_1106&dev_8501=c:\windows\inf\machine.inf pci\ven_1106&dev_8601=c:\windows\inf\machine.inf pci\ven_1106&dev_8605=c:\windows\inf\machine.inf pci\ven_1106&dev_b091=c:\windows\inf\machine.inf pci\ven_1106&dev_b099=c:\windows\inf\machine.inf pci\ven_1106&dev_b112=c:\windows\inf\machine.inf pci\ven_1004&dev_0005=c:\windows\inf\machine.inf pci\ven_1004&dev_0006=c:\windows\inf\machine.inf pci\ven_1004&dev_0101=c:\windows\inf\machine.inf pci\ven_1004&dev_0102=c:\windows\inf\machine.inf pci\ven_1004&dev_0103=c:\windows\inf\machine.inf pci\ven_1004&dev_0104=c:\windows\inf\machine.inf pcmcia\*pnp0600=c:\windows\inf\mshdc.inf pcmcia\exp___-pnpide-b0b3=c:\windows\inf\mshdc.inf pcmcia\kme-kxlc005-a99e=c:\windows\inf\mshdc.inf pcmcia\_-ninjaata--3768=c:\windows\inf\mshdc.inf pcmcia\fujitsu-ide-pc_card-ddf2=c:\windows\inf\mshdc.inf primary_ide_channel=c:\windows\inf\mshdc.inf secondary_ide_channel=c:\windows\inf\mshdc.inf *pnp0600=c:\windows\inf\mshdc.inf *azt0502=c:\windows\inf\mshdc.inf pci\cc_0101=c:\windows\inf\mshdc.inf pcmcia\lookmeet-cbide2______-6c0a=c:\windows\inf\mshdc.inf pci\ven_10b9&dev_5215=c:\windows\inf\mshdc.inf pci\ven_10b9&dev_5219=c:\windows\inf\mshdc.inf pci\ven_10b9&dev_5229=c:\windows\inf\mshdc.inf pci\ven_1097&dev_0038=c:\windows\inf\mshdc.inf pci\ven_1095&dev_0640=c:\windows\inf\mshdc.inf pci\ven_1095&dev_0646=c:\windows\inf\mshdc.inf pci\ven_1095&dev_0646&rev_05=c:\windows\inf\mshdc.inf pci\ven_1095&dev_0646&rev_07=c:\windows\inf\mshdc.inf pci\ven_1095&dev_0648=c:\windows\inf\mshdc.inf pci\ven_1095&dev_0649=c:\windows\inf\mshdc.inf pci\ven_0e11&dev_ae33=c:\windows\inf\mshdc.inf pci\ven_8086&dev_1222=c:\windows\inf\mshdc.inf pci\ven_8086&dev_1230=c:\windows\inf\mshdc.inf pci\ven_8086&dev_7010=c:\windows\inf\mshdc.inf pci\ven_8086&dev_7111=c:\windows\inf\mshdc.inf pci\ven_8086&dev_2411=c:\windows\inf\mshdc.inf pci\ven_8086&dev_2421=c:\windows\inf\mshdc.inf pci\ven_8086&dev_244a=c:\windows\inf\mshdc.inf pci\ven_8086&dev_244b=c:\windows\inf\mshdc.inf pci\ven_8086&dev_248a=c:\windows\inf\mshdc.inf pci\ven_8086&dev_24c1=c:\windows\inf\mshdc.inf pci\ven_8086&dev_24ca=c:\windows\inf\mshdc.inf pci\ven_8086&dev_24cb=c:\windows\inf\mshdc.inf pci\ven_8086&dev_7199=c:\windows\inf\mshdc.inf pci\ven_8086&dev_7601=c:\windows\inf\mshdc.inf pci\ven_1042&dev_1000=c:\windows\inf\mshdc.inf pci\ven_1039&dev_0601=c:\windows\inf\mshdc.inf pci\ven_1039&dev_5513=c:\windows\inf\mshdc.inf pci\ven_10ad&dev_0001=c:\windows\inf\mshdc.inf pci\ven_10ad&dev_0150=c:\windows\inf\mshdc.inf pci\ven_1106&dev_0571=c:\windows\inf\mshdc.inf pcmcia\ibm-microdrive-7f50=c:\windows\inf\mshdc.inf pcmcia\ibm-microdrive-aa55=c:\windows\inf\mshdc.inf pcmcia\cl_ata_flash_card_lexar__-hurric_-172f=c:\windows\inf\mshdc.inf pcmcia\cl_ata_flash_card_lexar__-tidalwv-0e97=c:\windows\inf\mshdc.inf pcmcia\____cl_ata_flash_card_lexar__-hurric_-dc37=c:\windows\inf\mshdc.inf pcmcia\cl_ata_flash_card_lexar__-tornado-29ec=c:\windows\inf\mshdc.inf pcmcia\cl_ata_flash_card_lexar__-tidalwv-fd21=c:\windows\inf\mshdc.inf pcmcia\lexarmedia_ata_flash_card-hur_hp_-0623=c:\windows\inf\mshdc.inf pcmcia\sony-memorystick(__4m)-e637=c:\windows\inf\mshdc.inf pcmcia\sony-memorystick(__8m)-9eb3=c:\windows\inf\mshdc.inf pcmcia\sony-memorystick(_16m)-d04d=c:\windows\inf\mshdc.inf pcmcia\sony-memorystick(_32m)-1766=c:\windows\inf\mshdc.inf pcmcia\sony-memorystick(_64m)-8c2c=c:\windows\inf\mshdc.inf pci\ven_1055&dev_9130=c:\windows\inf\mshdc.inf pcmcia\micron-mtcf____-392d=c:\windows\inf\mshdc.inf pci\ven_1179&dev_0105=c:\windows\inf\mshdc.inf ************************ Let me know if you have any more questions.
  7. ViperZ2000

    Question for you Win2k3 Server users

    How small is your "small" business? Active Directory is basically used to centrally manage your users, PCs, servers, access, etc. It's typically used in a MS Exchange email environment. I would recommend it if you have 50+ users and PCs (I don't remember the exact Microsoft recommended number). AD will not speed up your application but replacing your server, upgrading your network infrastructure, and/or client PCs may. You could always load up a test box, setup the app, and test a few clients on it to see if you notice any improvements. Good luck.
  8. Are you receiving the same error as shown by the text pasted into your post? I had difficulty until I set my page file min @ 512 and max @ 512MB. After that, reinstalling it fixed the issues. Good luck!
  9. Are you receiving the same error as shown by the text pasted into your post? I had difficulty until I set my page file min @ 512 and max @ 512MB. After that, reinstalling it fixed the issues. Good luck!
  10. As mentioned by Felix, I have the same setup for our sales force. OS Partition Data Partition Image partition Once per month, the system automatically reimages itself using Ghost. We have some scripts that look at some pre-determined files to rename the PC, setup outlook, and a few other apps. Patchlink is installed automatically after the reimage and it downloads all the MS patches and custom app updates from our patchlink server. I know that seems extreme, but setting them as power users does not help since they re-add some of our demo software. You can have their logins as power users and make an admin account for them to use when they REALLY need to install software. Good luck with it...
  11. ViperZ2000

    RAID 1 BOOT PROBLEM

    If I'm reading this correctly, you're using RAID1 (mirroring). Once you initially configured the mirrored set, it should have copied all of the data (and boot info) from drive0 to drive1. From then on, every single change would be "mirrored" to drive1. Now that drive0 was rebuilt from drive1, it should work just fine, provided the RAID card was performing it's job properly. If not, you may try to use Win2K with slipstreamed SP4 boot CD to repair installation.
  12. ViperZ2000

    Counter strike and Registry

    With CS 1.5, everything that you need is in the default folder of c:\sierra\ and in one registry spot, as shown below: ***************** [HKEY_CURRENT_USER\Software\Valve\Half-Life] "InstallPath"="c:\\SIERRA\\Half-Life" "Full Name"="Half-Life" [HKEY_CURRENT_USER\Software\Valve\Half-Life\Recent File List] [HKEY_CURRENT_USER\Software\Valve\Half-Life\Settings] "Version"=dword:00000001 "LauncherBPP"=dword:00000010 "LauncherWidth"=dword:00000280 "LauncherHeight"=dword:000001e0 "EngineGLDriver"="Default" "EngineD3DDevice"="Default" "EngineType"=dword:00000002 "EngineModeW"=dword:00000500 "EngineModeH"=dword:000003c0 "EngineModeBPP"=dword:00000010 "EngineModeCaptured"=dword:00000001 "A3D Support"=dword:00000000 "EngineModeWindowed"=dword:00000000 "CPUMHZ"=dword:00000000 "Key"="REPLACE THIS WITH YOUR KEY" "Mod Sort Order"="1;" "EngineMode"=dword:0000000d "3DWarning"=dword:00000001 ***************************************** If you reload, just copy this entire folder off, reload the OS, and dump this back into the same spot as before. As for the registry, save the above mentioned hives (or copy mine) and re-add to the registry. You can save mine by copying it into notepad and then saving it as a .reg file. Be sure to put your own HL CD Key in above. This will save time and headaches on reloads and PC swaps. Hopefully this helps.
  13. I have about 10 models of the IBM laptop and most require a unique image. How can I get one image to load on all of these laptops and work properly? I'm using the VLK version of WinXP Pro Corp and have Sysprep 2.0. I just need some clear steps. Also, no AD yet. I already have one of these IBM images that will be used as the master. Afterward, I'll plan on ghosting this up. Thanks!
  14. ViperZ2000

    Monitoring network speed

    DUMeter works fine to track an individual PC or Server. It would work fine if my network traffic flowed through a PC or server. I am just accustomed to using PRTG on my Cisco routers and it works great.
  15. ViperZ2000

    The best defraggers for disks and registry

    Quote: I have used Raxco PerfectDisk and O&O Defrag, both of which were very nice. PerfectDisk was really nice on drives that were both very full and very fragmented. As for the registry, I couldn't tell you too much about that as I rarely keep Windows client installs around long enough to care. Lol. Same here. PerfectDisk works great and I too barely keep an install of Windows around long enough. Usually, if I keep it around for more than a month or so, it's unusual.
  16. I've successfully setup and configured a Windows 2000 Pro SP4 distribution share that is fully unattended and working fine. I've created the same thing for XP SP1. I've made the distribution share (SERVER1\winxppro$) and assigned FULL ADMINISTRATIVE permissions to the share (for diag purposes only). I made the Unattend.txt file using the XP SetupMGR file also. I've copied the contents of my XPSP1 I386 dir to this share. I then bootup with the same IP boot disk, connect to this share and then launch the unattended.bat (renamed unatt-xp.bat) file. The XP setup starts but then gives the message similar to "setup cannot copy disk1 to the hard drive". If I skip this file and go to the next one, it does the same, all of the way thru the boot files. So, I look on my newly partitioned C: drive (3GB Fat32) and it shows a few new directories that were created by the XP setup program. I've even just browsed to \\server1\winxppro$\winnt and then manually typed the path to the setup files, it starts but then stops again at the same point. I've setup an XP distribution share before appx 6 months ago and have never had any problems. I've tried this at home from my own server and again on one of our file servers. Note: I've tried multiple PCs and all of the Win2000 unattended installs work fine on all...just the XP portion will not work. Any ideas?? :x
  17. ViperZ2000

    Windows XP - Networked Unattended Install

    Well, I deleted everything for a 3rd time and set it up again. It appears that XP unattended installs require a fat16 partition before it will actually work??? This is right? Once I formatted the partition using fat16 it worked. This was the case with all 3 machines (an IBM laptop, Compaq D51S desktop, and a Dell GX110).
  18. ViperZ2000

    Windows XP - Networked Unattended Install

    Yeah, I've tried 3 different workstations and also sharing it from another Win2K Server. The same machines that fail with the XP install work just fine when I run the Win2K pro installs.
  19. ViperZ2000

    Windows XP - Networked Unattended Install

    I've been using the slipstreamed CD since about 1 week after SP1 came out with no problems. However, that's a good point and something else for me to try. I just pulled out the original XP Pro disc, deleted the contents of the dist share, and then copied the contents of the original disc's \I386 dir to the xp dist share. Same thing..."cannot copy" message after about 5 seconds. It actually tries to start which is the weird thing. ***************************** UNATT-XP.BAT File: @rem SetupMgrTag @echo off rem rem This is a SAMPLE batch script generated by the Setup Manager Wizard. rem If this script is moved from the location where it was generated, it may have to be modified. rem set AnswerFile=i:\unatt-xp.txt set SetupFiles=x:\ x:\winnt /s:%SetupFiles% /u:%AnswerFile% ************************************* I already map the I: drive, which has my batch and unattended files in it (along with my ghost images). 1.) Once I'm at the (I:\) drive, I usually use a gdisk batch file (g-del.bat) to delete all partitions on the HD 2.) I then use g-cre XXXX where"xxxx" is the size of the new primary partition. It creates it, marks it active, and then quick formats it using FAT32. 3.) I reboot. 4.) So once I get back to the (I:\) dirve, I simply type "X" and it maps the (X:\) drive to my server\winxppro$ dist share. 5.) Once the drive is mapped, I type in "UNATT-XP" which launches my unattended XP batch file and uses the UNATT-XP.TXT answer file. I do this the same way as I do the Win2K SP4 network unattended installs. Any other suggestions???
  20. ViperZ2000

    Best way to install a new harddrive without losing info.

    LOL...now I see the date of the post. Somehow it showed up as a new post today. Oh well...
  21. ViperZ2000

    Best way to install a new harddrive without losing info.

    Quote: Right now one 40gig Maxtor 7200 UDMA 66 drive is $299 at Staples and one 20gig Maxtor 7200 UDMA 66 is $159. So it is going to cost a little more but make things easier on me. . That is WAY too high for a 20GB drive. You can easily get a 120GB drive for that. Check out www.pricewatch.com or even Best Buy on Sundays. They have 40GB drives for about $50 after rebates. Also, look for the 8MB cache models since they have a 3 year warranty, unlike the 2MB cache models with 1 year warranties. Hope this gets you more GBs or saves you some $$$
  22. ViperZ2000

    ICS With wireless

    ...or you have your main internet access via a wireless card from your PC. You want to use the onboard NIC to connect via a hard wire (CAT5) to your 2nd PC so that it can connect. You do not have the check box inside the wireless nic properties so that you can enable ICS. It sounds like the box is not there because the onboard or PCI NIC is not configured or has an issue. I'd start there and make sure both network cards are listed correctly in device manager (control panel/system) :x
  23. ViperZ2000

    ICS With wireless

    Windows 98 (I think...it's been a while), Windows 2000, XP, and 2003 Server all can handle what is known also as ICS (internet connection sharing). It basically uses NAT and allows multiple PCs to get out to the net using one routable address that your ISP gives you. General Win2000/XP ICS Config: 1.) Make sure both NICs are installed and have drivers loaded. 2.) Right click My Network Properties (or Network XXX in the control panel) 3.) Choose the NIC that is connected to the Internet 4.) Right click it and choose Properties 5.) Click Sharing 6.) Check the "Enable internet connection sharing..." box 7.) Press OK and then Reboot when prompted 8.) Bring up your second PC and it should be able to get out (if you are using a crossover cable OR a hub/straigt cable) Hope this is what you were looking for.
  24. ViperZ2000

    RAID performance issues

    Can you try setting your swap file to a fixed size? I think 1.5x your memory should be fine (768MB). Reboot and give it a try. Also, disable any virus protection (sigh-I know, I know), any disk defragmenters if scheduled, and other unnecessary items in the system tray. Have you reloaded your system from scratch? If not, I would recommend that you ghost your image to a temporary location (server or another HD) and reinstall XP, your VIA chipset driver first, then the remaining drivers. I would then ghost it again to a temp location on another PC so that you have a fresh image in case you ever need it. I would then install Neverwinter Nights and see if it still occurs. If so, take the one of your drives out of the array, plug the other into the standard IDE slot, then pull the image back down to it and see what happens. Still laggy, then try it with the other hard drive. This could even be from faulty memory, faulty memory slot, or even excessive paging. Hope this helps.
  25. ViperZ2000

    Win2000 Adv Server File Copy slow

    When I copy large files from 1 win2k adv server to another, available memory drops to about 10MB free on both. Most files are about 1GB each. It takes about 15-20 minutes to copy these from 1 server to another. Here's the specs of both: Dual PIII-1.13 1GB PC133 3Com 3c905b 10/100 (connected at 100) 300GB on an IDE RAID5 array (4x100WD JB drives) P4-2.4GHz 1GB PC2700 DDR Intel 10/100 onboard (connected at 100) 240GB on an IDE RAID0 array (2x120WD JB drives) Both are Win2000 Adv Server with SP3. They are connected on a corporate LAN by a Cisco switch. ** This also happens with a crossover cable also ** NICS have also been replaced/added to see if that was the issue. :x Any reason for the slow copy times?
×