Jump to content


  • Content Count

  • Joined

  • Last visited

About greyghost

  • Rank
  • Birthday 01/01/1970

Profile Information

  • Interests
  1. Depending on your system specs it may appair the SAS is hanging but it's not, Windows hives (registry) are rather large and complex. Have you actually just let it run be it seem to me not responding? or do you just cancel the scan? Let SAS run its coarse minimized and do other things, come back to it later. Let us know how you get on.
  2. Did not have any trouble with install, Mind you I installed OSS then SAS over the top.
  3. Have had no trouble with SAS & OSS at all, been running OSS since it rolled out in the 2009 format. Went from NOD32,OFW and SAS. No regrets it works great. Mav
  4. Are you getting any boot options from the CD? If set correctly the computer should automatically detect the inserted CD, and a message "Press any key to boot CD" should appear. if so refer to my first post on getting to the Recovery Console.
  5. Ok so atm it sounds like the CD drive is not set to first priority boot. and that has to be sorted before you try CD booting. Do you see the early boot detection screen? if so Do you know how to get into bios and set CD boot priority? Ok I am not going to type a longe session here if you dont know how to, sorry have to go shopping (wife.nag.married32dll infection). http://www.hiren.info/pages/bios-boot-cdrom <-- that will give you some guidance. Good luck
  6. You could try a Master Boot Record repair. Boot with the XP installation CD. When prompted press R to repair Windows XP installation. You may be presented with a host selection if you were running a duel boot system so press 1 to select XP. When and if prompted enter the administrators password. You should be at the recovery console. Type in without the quotes... "fixmbr" hit enter. quite a few warnings will pop up Type "y" (no quotes) and hit enter to carry out the MBR repair. Type exit and hit enter to leave the recovery console and reboot. You may have a booting HD again. Good luck.
  7. greyghost

    Hey AdvancedSetup, I appreciate the help on this (all those sexy log files), or it would have taken forever. Have not had much time on my hands to post or reply to a lot of requests. (It's motorcycle session down here. So hey you know..... Priorities and all ) Finding all the info posted there for me to chew on was a blessing. So hey no toes were stepped on as far as I am concerned, we are all here for the same reasons, to help and be helped and get results. Take it easy out there GG (aka Mav)
  8. greyghost

    It was a team effort Oliver, that's what we are all here for in the end As for that driver file, delete it. if there are any other dll's or left overs floating around, without the driver installed and running they are dormant. The next step is a total MUST do to make sure this driver is out and gone for any restore points. In control panel, go to the System cpl, select the System restore tab, "Turn off System Restore on all drives" Apply ans ok everything. Make sure you delete that port135sik file in system32 folder. Do a full scan with SAS and with your AV. Reboot the system, Do another scan with SAS, go back into the System.cpl in control panel, and turn on system restore again. Then go to the start menu programs - accessories - system - system restore and create a fresh restore point. Merry Xmas
  9. greyghost

    Lets not get the man uninstalling legit software that at the moment has absolutely nothing to do with the issue. Lets get him up and running first then trim the fat C:\WINDOWS\system32\drivers\port135sik.sys otherwise know as systemntmi.sys and a few other alias's. You have a background service running on the system, in other words a rootkit. You need to at the moment in safe mode rename that file to something like port135sik.123, yeah deleting it is obvious, but just at the moment the rename is safe until we know you can get rid of it completely. Try a reboot, you may need to eliminate some files that could be related to it.
  10. greyghost

    Oliver, once you are in safemode, can you access the run command and type in "msconfig" and hit enter. in the General tab, select Diagnostic Startup, apply and ok then reboot. and see if you can boot. You could also try selective Startup and each time it fails untick a boot item. Also the startup tab, you can one by one untick and eliminated them. I know its a laborious mission ahead of you. But short of doing a Repair install these options are worth a try. The thing is you still have an operational OS there if you can boot into safe mode, sounds more like a driver is at fault or been corrupted by the infection. Give it a go, and get back with any results pls.
  11. I don't usually get on the defensive or Attack band wagon. But what are you trying to say??? Are you looking for someone to blame for you installing malware on your system and trashing it. If you had no real time anti-malware running when you installed that crap (AV2009) then the system was doomed to be trashed right there and then. Installing AV/AM after the damage is done is just a fingers crossed last chance scenario that very rarely works out for the best. The first line of defense is user common sense, then it comes down to security apps. Stop trying to point the finger at someone for what was your actions in the first place.... You have been given good advice.... So Bite the bullet and repair or reinstall the OS. That's about all the choices you have.
  12. Happy to help. Am a bit concerned with the "Life saver..." quote. Surely your wife was not that angry
  13. redwolfe try doing a properties on the sasenum.sys file, check the securities tab. Make sure all your user groups ie: Administrators, Power Users, SYSTEM and Users all have at least a minimum of "Read" and "Read & Execute" permissions. Worth a try. edit I just noticed you are running HIPs "system safety monitor" have you tried disabling that, as it could be restricting the running of the driver in lesser permission modes.
  14. 2 things to try. Once in safe mode. Start menu, select "run" In the Run box, type "msconfig" without the quotes and press Enter. Click the "BOOT.INI" tab, and uncheck the box, "/SAFEBOOT", Apply, OK You may find that the "/SAFEBOOT" is actually unchecked. In the top box you will see the boot statement, it should read along the lines of [boot loader] timeout=8 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect it may have an addition added to it with "/SAFEBOOT" if this is the case it needs to be edited and the "/SAFEBOOT" qualifier removed. To do this goto start menu select run, type in without the quotes "notepad c:\boot.ini" hit enter. remove the /SAFEBOOT statement so you have only.. [boot loader] timeout=8 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect Save and reboot. you should be home and on your way. Please take care when editing. No responsibility for user errors. Good luck. And remember if If you want to boot into safe mode or any other mode, F8 does NOT alter system files...
  15. And yet the whole truth was not told, the omnibox is just an extension of the already installed google search box that is standard in Firefox, Safari (for a very long time now), and now IE7-8b. They also submit as you type. Unfortunately blog jurno's are the same as any others out there, they give up the truth for a bit of sensationalism. If you want the latest then use the link that emperordarius has posted. Note the versions there are "Chromium" the Open source base code that "Google Chrome" is built on. Hopefully with all this generated hysteria going on, my shares in Monofoil will climb On a side note, Chromium (Chrome) is a very nice, fast and slick browser to use. Very elegant indeed.
  • Create New...