Recently got a new laptop with the 64-bit version of Vista Ultimate pre-installed. Usenet Explorer was one of the first programs I installed, and for the most part works great.
I have run into one issue though: I get the fatal bluescreen error message occasionally. I finally figured out how to keep the error on the screen instead of auto-rebooting so that I could see what it said. It references a system file called ‘fltmgr.sys’ as being part of the issue.
It only happens when Usenet Explorer is running and downloading queued up files. I don’t recall it happening when downloading headers, just the files. It doesn’t occur every time Usenet Explorer is running, but every time it has happened – it was running.
Anyone else run into this?
Usenet Explorer & Vista (Kaspersky antivirus)
Update: It's gotten worse. As I got no response here, I've just continued using the product (there is nothing better). The crashing has continued, though with the last one I can no longer establish online activity. If I try to get new headers, or download, nothing happens. No errors, just no activity.
If I try to 'download and save body' it asks as before if I want to delete the body once saved, I answer yes -- and nothing happens. Same with any function that involves going online. Nothing wrong with my connections...
Any ideas....?
Edit: After sending the message, I checked the servers tab -- both the servers I use are gone. Getting frustrating -- guess UE isn't fully Vista compatible at this point
If I try to 'download and save body' it asks as before if I want to delete the body once saved, I answer yes -- and nothing happens. Same with any function that involves going online. Nothing wrong with my connections...
Any ideas....?Edit: After sending the message, I checked the servers tab -- both the servers I use are gone. Getting frustrating -- guess UE isn't fully Vista compatible at this point
It also could have something to do with memory failure, memory management, disk management or whatever Vista has to do to get and store articles and headers. If something gets corrupted by the operating system, no program will be able to run as designed.
It would not be the first major screw up by Microsoft...
It would not be the first major screw up by Microsoft...
Dutch? Visit the Dutch UE/Newspro forum at: http://www.binaries4all.nl
Nederlandse UE handleiding op http://www.binaries4all.nl/ue
English UE tutorial online at http://www.binaries4all.com/ue/
Handy links at: http://jpfx.zapto.org/
Nederlandse UE handleiding op http://www.binaries4all.nl/ue
English UE tutorial online at http://www.binaries4all.com/ue/
Handy links at: http://jpfx.zapto.org/
Anything's possible I guess. It is a brand new system, works fine otherwise -- as mentioned in my first post, it only crashes when UE is running. I've no disk or memory management products installed, it's jsut the standard Vista stuff. Thanks though...
jaapf wrote:It also could have something to do with memory failure, memory management, disk management or whatever Vista has to do to get and store articles and headers. If something gets corrupted by the operating system, no program will be able to run as designed.
It would not be the first major screw up by Microsoft...
I guess the author is busy -- maybe a much deserved vacation, was hoping for a little insight. For lack of anything else to try, just started over. Deleted the database, removed the program and re-installed to a new directory. Doing that initial lengthy header download now, maybe it was just a little bit of data corruption or something...
I realize in many ways it's better to wait for the first SP to come out, but something as basic as this shouldn't be a reason. And... the program is listed as 'Vista Compatible' at the home page for the product.
Thanks for the troll post though.
Thanks for the troll post though.
Josef K wrote:The problem is Vista itself. It's not ready yet. If you can, install XP and try Vista again when SP1 is out and they might have it halfway ready for a worldwide release. That's the short and sweet answer and that what I advise all my customers.
Any flaws in particular that might apply to this situation? I'm assuming you must have some examples since you took the time to respond here, either that or you're just trolling...
Josef K wrote:Troll? It's widely regarded that Vista is flawed. If you want to fight with it then that's your choice but I have a right to express my opinion. An opinion which is shared by a great many others in the field of IT.
By the way, UE is Vista compatible. It's just that Vista is crap.
I'm not about to get into an argument over something as trivial as this. You registered in 2003 (a little while after I joined on the first day this forum was opened) so you've had plenty of opportunity to see all of my posts and know for a fact that I'm no troll. I've done nothing but try to help people here. Since you can't appreciate that then you should do some research on your own. This will get you started on something specific to your situation. Remember, it's simple, quick and easy to do a search on the web with just a couple of relevant keywords.
Anyway it's 3:15 here so time for bed for me. Good luck with your hunt for information - I'll leave you to it.
Anyway it's 3:15 here so time for bed for me. Good luck with your hunt for information - I'll leave you to it.
No argument here, just looking for useful info. I actually did try to research this before posting here, got a lot of hits on the fltmgr.sys, but none of the info seemed to directly apply. I didn't upgrade a system, it shipped with Vista (and sata drives, which seems to be an issue with a lot of upgrades in a dual-harddrive-type).
It's great you've got a good posting record here, hopefully you'll run into some info applicable to this topic -- would be most welcomed
Will see how it goes now that I've reinitialized everything, with luck it was just some file corruption and is all cleared up now. UE is so much better than the competition...
It's great you've got a good posting record here, hopefully you'll run into some info applicable to this topic -- would be most welcomed
Will see how it goes now that I've reinitialized everything, with luck it was just some file corruption and is all cleared up now. UE is so much better than the competition...
Josef K wrote:I'm not about to get into an argument over something as trivial as this. You registered in 2003 (a little while after I joined on the first day this forum was opened) so you've had plenty of opportunity to see all of my posts and know for a fact that I'm no troll. I've done nothing but try to help people here. Since you can't appreciate that then you should do some research on your own. This will get you started on something specific to your situation. Remember, it's simple, quick and easy to do a search on the web with just a couple of relevant keywords.
Anyway it's 3:15 here so time for bed for me. Good luck with your hunt for information - I'll leave you to it.
blue screen means some system issue like driver crash
http://www.google.com.ph/search?hl=en&q ... rash&meta=
e.g.
http://www.vista64.net/forums/vista-ins ... creen.html
ue doesn't have drivers, so must be something third party, probably network related or a driver which is hooked to threads of execution creation/exiting.
but again there are many other reports on google, may be bug in vista as well but it is not so likely, most likely a third party driver causes crash in a system modlue. ue itself cannot cause crashes directly since it is not running in the system mode, it is 100% pure application so it cannot cause system blue screens itself.
you need to check it running on a clean system to verify whether it is vista to blame - it might be well caused by third party driver like that of third party firewall or antivirus, if ue runs on a clean system but the problem starts when you install a third party application it means the latter is to blame, in vista writing drivers is different from older systems so also there bugs are more likely.
in short the solution is to uninstall applications which install drivers (like third party firewalls) until the system crashes stop so the culprit will be identified. or you can also start with a clean system and install those applications one by one until the system crashes start.
if the bug in a third party driver is caused by keeping track of open/closed sockets you may just try to uncheck "edit menu->properties->general->keep alive" so sockets will be closed in the thread which created them to bypass the buggy driver code.
http://www.google.com.ph/search?hl=en&q ... rash&meta=
e.g.
http://www.vista64.net/forums/vista-ins ... creen.html
ue doesn't have drivers, so must be something third party, probably network related or a driver which is hooked to threads of execution creation/exiting.
but again there are many other reports on google, may be bug in vista as well but it is not so likely, most likely a third party driver causes crash in a system modlue. ue itself cannot cause crashes directly since it is not running in the system mode, it is 100% pure application so it cannot cause system blue screens itself.
you need to check it running on a clean system to verify whether it is vista to blame - it might be well caused by third party driver like that of third party firewall or antivirus, if ue runs on a clean system but the problem starts when you install a third party application it means the latter is to blame, in vista writing drivers is different from older systems so also there bugs are more likely.
in short the solution is to uninstall applications which install drivers (like third party firewalls) until the system crashes stop so the culprit will be identified. or you can also start with a clean system and install those applications one by one until the system crashes start.
if the bug in a third party driver is caused by keeping track of open/closed sockets you may just try to uncheck "edit menu->properties->general->keep alive" so sockets will be closed in the thread which created them to bypass the buggy driver code.
I am a professional software developer. 64 bit operating systems are more sensitive then the 32 bit versions, both XP and Vista. It is typically an issue with drivers. While I have a dual core at work and home I only run the 32 bit versions, and they run just fine. Maybe in a year or so the 64 bit versions will be better. Frankly, I don't think you will see much difference if you go back to the 32 bit version.
I know, 64 bit is better than 32 (heck it is twice as good, 32 * 2 = 64) and we have to have the best, right?
I know, 64 bit is better than 32 (heck it is twice as good, 32 * 2 = 64) and we have to have the best, right?
i got a similar report from another user, in both cases (i have info from the original poster as well through a private message) they both have kaspersky antivirus, so a kaspersky driver is the cause of the problem.
the second user has 32 bit vista installation so it is a common bug in the current version of a kaspersky driver for both 32 bit and 64 bit vista (at least).
unchecking properties->general->keep alive stops those crashes, it means with the option unchecked the driver bug is not or unlikely to be triggered.
so the kaspersky driver bug is in managing connections that outlive the thread which created them, probably they'll fix it shortly, since it is an apperent bug.
i edited the subject to make it more clear, so this particular matter is closed.
the second user has 32 bit vista installation so it is a common bug in the current version of a kaspersky driver for both 32 bit and 64 bit vista (at least).
unchecking properties->general->keep alive stops those crashes, it means with the option unchecked the driver bug is not or unlikely to be triggered.
so the kaspersky driver bug is in managing connections that outlive the thread which created them, probably they'll fix it shortly, since it is an apperent bug.
i edited the subject to make it more clear, so this particular matter is closed.