Jump to content

FrankenBox

Advanced Member
  • Content Count

    1,493
  • Joined

  • Last visited

About FrankenBox

  • Rank
    Advanced Member
  • Birthday 11/12/1977

Contact Methods

  • AIM
    Crazy Forrest
  • MSN
  • Website URL
    http://
  • ICQ
    337191118
  • Yahoo
    forrest_pugh

Profile Information

  • Gender
    Male
  • Location
    Right where I am

Previous Fields

  • System Specifications:
    Big. Square. White with various stains on the face plate.
  • Teams:
  1. It's.... ALIVE!!!

  2. "[email protected] made it that because Peewee was my nickname in the Air force."
  3. Thanks.... looks tricky... not too many places seem to have solid info on it yet.
  4. Results from Virustotal: File UD6DD1.EXE received on 08.04.2008 10:40:49 (CET) Current status: finished Result: 1/36 (2.78%) Compact Print results Antivirus Version Last Update Result AhnLab-V3 2008.7.29.1 2008.08.04 - AntiVir 7.8.1.15 2008.08.04 - Authentium 5.1.0.4 2008.08.03 - Avast 4.8.1195.0 2008.08.03 - AVG 8.0.0.156 2008.08.03 - BitDefender 7.2 2008.08.04 - CAT-QuickHeal 9.50 2008.08.02 - ClamAV 0.93.1 2008.08.04 - DrWeb 4.44.0.09170 2008.08.04 - eSafe 7.0.17.0 2008.08.03 - eTrust-Vet 31.6.6002 2008.08.02 - Ewido 4.0 2008.08.03 - F-Prot 4.4.4.56 200
  5. Might not be as simple as that... I lost ME7244.exe when I switched back to normal startup to see if it would start because the file search couldn't locate it. I did not find it starting up again, but got a nother bogus looking one... LNAFE2.exe Similarly there does not seem to be a listing for it. Right now it is sitting open on my taskmanager but the file search is not able to locate it. Unless it is a network file (in which case H*($S*#* we have big problems here), I think it might be an alias name for another process. I keep seeing symantec find the same trojan threats ove
  6. I'm helping to clean up a work machine that is very very sick while our IT guy is away. Found a number of trojans so far, a few nasty malware pranks, and some rogue .exe files that I can't seem to place. Mostly clean now, but I have two processes running that are suspicious. msiexec.exe is automatically loading when windows boots, although there are no residual installation processes due to complete. ME7244.exe is running and I am not sure what that is... further, there is no google info on it. I am considering it a very likely candidate to be a trouble maker. Does any
  7. could be that your system preferences are set so that all new dialogs and processes are forced to open into a new window. I have seen it floating around somewhere before, but cant remember exactly where. It's a system setting - check your control panel. Or perhaps someone knows exactly where this option is.
  8. The PSU might read as good, but might not have the necessary capacity to run all the hardware, especially with newer graphics cards.
  9. Have you disabled the onboard video controller in your BIOS? If not, you will effectively running a dual monitor machine, and the onboard controller will try to be the primary - you won't see anything unless you plug into the onboard jack. If not that, try what dickster says - it's most likely just a power issue.
  10. My recommendation for a fix would be to address the warning logic about system restore size. I think the average size of drives may be higher than stated, however if this is not the case, try benchmarking against a relative percentage of drive space. I have my system restore set almost to minimum (1%) and due to my drive size this is still almost 6000 MB- Would I like to have this space back? Sure, but unless I take the time to look up the setting in my registry my choice is 200MB (two or three points), or 6000MB. I can't say I love the new layout, but after playing a little bi
  11. AH! Graphics card issue most likely. reference here. It seems the problem is that a WinXP SP1 install will not support PCI-E graphics cards. (I was wondering why I had similar problems with mine when I set it up - finally took it too a shop to configure the raid and install for me). Since this is a laptop (?) you may have the option in Bios to select a basic (onboard) graphics option and go through the install, upgrade and then reintegrate your upgraded graphics contoller. Incidentally - SP1 will not support USB2 either, which may or may not be an issue for you.
  12. Well then we are more likely getting down to a faulty or locked disc...
  13. Depends on how bad you need what is in the upgrade. I had no problems installing it, but since I run a machine that depends on a lot of legacy apps from older windows OS' and some old DOS code I ran into problems with the new service pack rendering those useless. You may find certain changes to settings and the way things are layed out that you may not like. It's more a question of do you really want it rather than do you really need it.
  14. If the disk is clean and scratch free, the next thing I'm wondering about the possibility of a memory problem. Sounds like there is not enough functional memory for XP to load. Even with a scratched disk, I have never had problems with BSOD right from the start. If the memory is not bad you can try the following: Boot down, disconnect all power cords or batteries, depress the power button for a few seconds to drain any residual charge from the board. What I am suspecting is the possibility of a hung thread. Your memory is not clearing it during a normal power up cycle, and s
×
×
  • Create New...