Jump to content

ravashaak

Member
  • Posts

    162
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by ravashaak

  1. If for some reason Ad-Aware doesn't solve your problem, try Spybot Search & Destroy. - Ravashaak
  2. I'm using Firefox 0.9.3 and it's working just fine for me. - Ravashaak
  3. Do both domain controllers have NetBIOS over TCP/IP enabled? Some general troubleshooting advice: 1. Thoroughly review the event logs on each DC. 2. Test connectivity by pinging each dc from the other one. 3. Perform an nslookup on each DC for the other DC. 4. Run dcdiag and netdiag on each DC. 5. Run ipconfig /all on each DC. 6. Other stuff, depending on results from above tests. - Ravashaak
  4. Well, since your original XP cd could install drivers for your RAID setup, and your new unattended CD cannot, it sounds as if these drivers were removed from your unattended CD. Did you perhaps (either manually or by some other means) remove some CD contents when making your unattended CD (perhaps to reduce the size)? If so, this could cause your problem. There are two things you can do to correct this. First, you could try and determine what was removed, and then add it back to your unattended CD. Or, you could follow the instructions here. The link above will instruct you on how to integrate your RAID controller drivers into your unattended CD. You'll just need to download the proper drivers from Abit's website. Good luck, and let me know if you run into trouble. - Ravashaak
  5. Pegasus, because it's a good fit for my environment.
  6. I've yet to mess around that much with network installs, although I have performed a couple in the past. However, I plan to delve more deeply into the topic soon just to broaden my experience. Your info should prove valuable. Thanks eth0. - Ravashaak
  7. Is this server a domain controller for an AD domain? If so, then perhaps you should try logging on with an account that is a member of domain admins before making this change. - Ravashaak
  8. Before I go spewing possibilities, what exactly do you mean when you say "contact"? - Ravashaak
  9. You could perform a repair install. I was forced to do this once to a system at work in order to correct the exact same symptoms. I swapped and reinstalled NICs, and even removed and completely reinstalled tcp/ip and everything else related to networking that I could find. Nothing corrected the problem. I never did isolate the exact cause, but the system is still running today, and the repair install was performed over a year ago. Of course, your mileage may vary. Good luck. - Ravashaak
  10. I was up for 76 hours back in 1991 . When everything wore off , I crashed for 16 hours, got up for one, then went back down for another 4 hours. I slept like someone hit me in the head with a hammer.
  11. Google that exact error phrase (just enclose it in quotes when you search). You'll find alot of info on the subject, from both MS and non-MS sites. You'll also find that alot of people encounter this same error message scenario. Argon007 is correct in saying your registry is corrupted. Sometimes this is recoverable and sometimes it is not. In my one past experience with this error, I was able partially recover the system via the recovery console. I was then able to backup my most important data. However, I eventually was forced to wipe and load since the problem kept repeating. I wish you luck. - Ravashaak
  12. Leave it to me to say the things that generally go without saying. However, having said that, now would be a good time to make sure you have a good backup of your important data. You've tempted fate once now, and escaped by the barest of margins. Next time, will you be so lucky? - Ravashaak
  13. My own preference (and perhaps not yours!) is to disable Windows XP's built-in zip file support and use a third-party program such as WinZip. If the same is true for you, you can do the following the disable it: Start --> Run, then type the following in the run box: regsvr32 /u %windir%\system32\zipfldr.dll If you later decide to re-enable this feature, then do the following: Start --> Run, then type the following in the run box: regsvr32 %windir%\system32\zipfldr.dll - Ravashaak
  14. Hmmm. It *may* be possible to perform this by using an inf file. Not that familiar with that particular method. I've been meaning to learn it as well, but there never seems to be enough time in my day. Anyone clarify if this would work for using system variables (such as %systemdrive%) to tweak the registry via inf file? - Ravashaak
  15. Appdeploy link corrected. Sorry folks. I was pretty distracted during that post. My teenaged stepdaughter had two of her teenaged friends sleeping over last night. As you can imagine, it sounded like a buncha geese in here. Talk about distractions! <babble> - Ravashaak
  16. LiquidSage's advice should work pretty well. I've used the same method for years now with no problems. You can also edit the appropriate registry key(s) for the same effect. The following link explains the different keys in detail. Even if you don't want to use direct registry editing in your situation, it might prove valuable to learn a little bit about what actually occurs behind the scenes when you use msconfig. http://support.microsoft.com/default.aspx?...kb;EN-US;179365 - Ravashaak
  17. I know there are some Cox Cable areas in Louisiana as well. - Ravashaak
  18. Here's another link (in case the first one doesn't quite cut the mustard): http://www.microsoft.com/technet/Security/...g/06tmplts.mspx - Ravashaak
  19. As far as I know, you can't use variables such as %systemroot% or %systemdrive% for registry tweaking. - Ravashaak
  20. Try the advice at this link: http://www.appdeploy.com/tips/detail.asp?id=72 I haven't verified it myself, so let me know how it works. - Ravashaak
  21. Additionally, if you want to perform this via the registry (nice for your unattended installs ), the registry key is as follows: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "forceguest"=dword:00000000 - Ravashaak
  22. SED can be used to edit text files from the command line. Originally a UNIX utility, it is now available for use in a windows command line environment. Just download the zip file from the url below and extract the sed.exe file. Next, place the file in your %systemroot%\system32 directory and you should be good to go. It may take a little practice to get the hang of this command's syntax, but once you do, you'll have a powerful and extremely handy new tool. If you get stuck, do a web search for sed tutorials or maybe sed syntax. Here's the link: http://unxutils.sourceforge.net/UnxUtils.zip Best of luck! - Ravashaak
  23. I *think* this is more of a connectivity issue between your computer and whatever website is hosting the images in question, rather than an IE issue. However, that's more of a guess on my part. - Ravashaak
  24. I really hope that MS integrates this feature into XP at some date. Having to force users to log off just so you can log on and make a few changes is ridiculous. This capability has been native to other OSes for ages now. It's my one ENORMOUS pet peave with XP and one issue that I feel hamstrings XP in comparison to other (non-MS) business-environment OSes. - Ravashaak
  25. The win32 version of sed may also be useful in such a situation. - Ravashaak
×
×
  • Create New...