RE: winblow startup help |
||
 Tr flamebalrog On 2005-05-14 16:40:51, adtrace wrote > [...] >[code]Cannot find a device file that may be needed to run Windows or a Windows application. When you read "device", think "service" (see why later). >The windows registry or SYSTEM.INI file refers to this device but the device file no longer exists. Most of the time, the registry is the place to go. >If you deleted this file on purpose, try uninstalling the associated application using its uninstall or setup program. "Mr. Operating System, please tell this to Symantards, not to me." >If you still want to use the application associated with this file try reinstalling that application to replace the missing file. No, thank you. >C:\PROGRA~1\SYMANTEC\SYMEVNT.386 >Press a key to continue > > [...] > >C:\PROGRA~1\NORTON~1\SAVRTPEL.VXD > >C:\PROGRA~1\NORTON~1\SAVRT.VXD > Good, you had enough time to write the names down (won't tell you my story, but just know it's not always the case). > So it does boot up but for one this is highly irritating, and for two, I really need to get my antivirus up on my comp. I've checked through my SYSTEM.INI file and neither "SYM" nor "SAV" is anywhere in there so I've no fucking clue where/what the problem is. But I need to get this sorted. You don't say you checked the registry, so I'll assume you didn't. >The asstards as Symantec told me to run the uninstall (after I had written in my initial email I had uninstalled and encountered these problems). They're a gifted bunch. And some criticize free software saying there's no support... >Any more intelligent help? More intelligent ? Not sure. Just basic stuff. Let's go... (pseudo)Devices require drivers. Information about starting drivers (most of them) is stored with informations about starting services. So, run regedit (or regedt32), and go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\. You can have a quick look at the names of the keys you see to determine if some could have been created by Symantec's product. You can check them. But as some names may not be of any help, just go to "Edit/Search...", check the "Value" checkbox, type the name of one of the files and click OK. If it does find one of the VXDs, it will probably be in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\VxD\ (but I don't know). If you find the correct key, change the associated "Start" value to 4 (or delete the whole key, it's up to you, but I would just change it). Repeat the same steps with the other files, with the "ControlSet002" key (and eventually others), and also try searching in the whole registry (you may need this for the ".386" file). If you've modified the "Start" value in all "ControlSetXXX" keys, then it's useless to do it in the "CurrentControlSet" one (as it's just an alias to the "ControlSet" currently in use). I'm not quite sure about the ".386" file, so it's not a bad idea to run a file search to find any reference to it (search for files containing "symevnt.386"). If you don't know what to do with what you've found, just post the results here (file names/path, what's inside, etc). Reboot. Check the registry again : I've seen some fsckin' software re-enabling their drivers in the registry. If this is the case, tell us about it. It's all I can do atm (I don't have any Symantec product to play with, sorry ;) ). I hope this helps, FB. PS 1 : next time, save your registry before installing such a product (antivirus, firewall, driver, any close-to-the-system/kernel stuff), then save it again after installing/rebooting and compare them. You'll save some time if something is fscked. PS 2 : burn a Windows live CD if you can. It helps a lot when your system won't let you do anything and crash/reboot as soon as it cannot handle a fscked up registry key (see "Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD", it's really easy to do and works perfectly). - Is it a feature or a bug ? - Replies:
|
||
| CyberArmy::Forum v0.6 Generated In 0.02483 seconds |
2005-05-14 16:40:51
2005-06-15 23:36:39
2005-05-14 16:59:12