If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Damaged Certificates, ZA free, and AVG dysfunction?
After following mae's suggestions of correcting your date and time (and check your
time zone too), reboot, and post back with what issues still exist. As for the OE settings for expanding threads and opening news messages, click Tools menu Options Read tab, and select them there. ....Glen, with one "n" :-) -- Glen Ventura, MS MVP Shell/User, A+ http://dts-l.org/ http://dts-l.org/goodpost.htm "et" wrote in message ... First, sorry to pile this all into one post, esp since it might best go to the OE ng, but it is more than that . . . After a PSU (rel new, 6 mos., Antec) failure last Saturday which caused no damage since it simply refused to start the next day, I found that AVG refused to load, telling me I had to upgrade to 7.5, and ZA Free wouldn't start either, saying some root certificates were probably damaged. ZA wouldn't uninst, same message, and after using Martau's TUn (old free version), it was still there, much as mentioned by, I think, Glenn Ventura in a thread some time back. I ended up weeding it all out, much as I remembered the ZL web site describes, then still found it was there (SpyBot TeaTimer told me), found the last few pieces, and then, finally found glee's post saved from that thread, with the important part of renewing the certificates, which I did--strange process, that--reloaded ZA Free (last W98 compatible version) and then downloaded the new AVG. But I decided with all this mess, I'd best uninstall the old, and install fresh. Did that, but it keeps saying the database, last updated on 11/9/06 is 1826 days old and is thus unsafe--Red flagged, etc. The icon's in the tray, but I'm not certain it's truly active, and this is suspicious, anyhow, and it makes no difference trying to update. When I tried to log on to the AVG free forum, it wouldn't accept my logon, and when they sent me a new password, it wouldn't accept that or the next one either. So no AVG forum. First thing I found was that every time I open OE under my identity, it says the server's certificate doesn't exist, but allows me to connect when I click on it. Then, I find, although it appears to be downloading new headers, it never displays them. So I set up my wife's identity to look at win98_gen_discussion and sure enough, they display. But even stranger, clicking on a header immediately displays the message in the preview pane (mine has always required spacebar or clicking on the "link" in the pane) *and* none of the threads are expanded (mine always were). I thought there was an option for that somewhere but can't find it. Anyway, the questions I'm asking are, what could cause the certificate damage like that? What sort of mechanism would cause *just* my OE identity to question the certificate for the ISP server, when it doesn't on *this* identity (my wife's). How could anything like this damage my OE identity? Does anyone know of strange AVG behavior (the update question) like that? Or the forum password difficulty? Incidentally, I think it pretty poor practice to deactivate the old version simply because they weren't supporting it anymore--would make much more sense just to warn. Mainly, I'd like to understand a little about what went on here, and how these certificates work, as this all came as something of a surprise. Malware is a *little* unlikely--I'm on dialup, and the most risky sites the machine ever visits is the comics site my wife visits to read '9 chickweed lane' every Saturday. I ran a SpyBot scan with clean results and will try some others (e.g., David Lipman's Rx) as I can find the time, but I'm hoping someone has some specific ideas on this. Apologies for the rambling length of this. Thanks, Joe (jt3) |
#2
|
|||
|
|||
Damaged Certificates, ZA free, and AVG dysfunction?
Thanks, Mae. Should have thought a little before I pushed the panic button,
eh? Joe "mae" wrote in message ... Your date is showing as year 2011. Correct and should be ok. -- mae "et" wrote in message ... | First, sorry to pile this all into one post, esp since it might best go to | the OE ng, but it is more than that . . . After a PSU (rel new, 6 mos., | Antec) failure last Saturday which caused no damage since it simply refused | to start the next day, I found that AVG refused to load, telling me I had to | upgrade to 7.5, and ZA Free wouldn't start either, saying some root | certificates were probably damaged. ZA wouldn't uninst, same message, and | after using Martau's TUn (old free version), it was still there, much as | mentioned by, I think, Glenn Ventura in a thread some time back. | | I ended up weeding it all out, much as I remembered the ZL web site | describes, then still found it was there (SpyBot TeaTimer told me), found | the last few pieces, and then, finally found glee's post saved from that | thread, with the important part of renewing the certificates, which I | did--strange process, that--reloaded ZA Free (last W98 compatible version) | and then downloaded the new AVG. | | But I decided with all this mess, I'd best uninstall the old, and install | fresh. Did that, but it keeps saying the database, last updated on 11/9/06 | is 1826 days old and is thus unsafe--Red flagged, etc. The icon's in the | tray, but I'm not certain it's truly active, and this is suspicious, anyhow, | and it makes no difference trying to update. When I tried to log on to the | AVG free forum, it wouldn't accept my logon, and when they sent me a new | password, it wouldn't accept that or the next one either. So no AVG forum. | | First thing I found was that every time I open OE under my identity, it says | the server's certificate doesn't exist, but allows me to connect when I | click on it. Then, I find, although it appears to be downloading new | headers, it never displays them. So I set up my wife's identity to look at | win98_gen_discussion and sure enough, they display. But even stranger, | clicking on a header immediately displays the message in the preview pane | (mine has always required spacebar or clicking on the "link" in the pane) | *and* none of the threads are expanded (mine always were). I thought there | was an option for that somewhere but can't find it. | | Anyway, the questions I'm asking are, what could cause the certificate | damage like that? | | What sort of mechanism would cause *just* my OE identity to question the | certificate for the ISP server, when it doesn't on *this* identity (my | wife's). | | How could anything like this damage my OE identity? | | Does anyone know of strange AVG behavior (the update question) like that? | Or the forum password difficulty? Incidentally, I think it pretty poor | practice to deactivate the old version simply because they weren't | supporting it anymore--would make much more sense just to warn. | | Mainly, I'd like to understand a little about what went on here, and how | these certificates work, as this all came as something of a surprise. | | Malware is a *little* unlikely--I'm on dialup, and the most risky sites the | machine ever visits is the comics site my wife visits to read '9 chickweed | lane' every Saturday. I ran a SpyBot scan with clean results and will try | some others (e.g., David Lipman's Rx) as I can find the time, but I'm hoping | someone has some specific ideas on this. | | Apologies for the rambling length of this. | | Thanks, | | Joe (jt3) | | | | |
#3
|
|||
|
|||
Damaged Certificates, ZA free, and AVG dysfunction?
Thanks, Glen. (easier not to make mistakes of that sort with the example
right in front, yes? Sorry about the 'n'.) As I replied to Mae, I should have thought a bit before I pushed the panic button. But a PSU failure can induce that sort of thing, I think. But I must admit that I had no idea before this happened that DUN checked the ISP server for a certificate upon connecting. Anyhow, retrospectively, 20/20 of course, it makes much sense. If I had no more trouble from the failure than a little corruption of the CMOS, I guess I'm pretty lucky. Actually, this all started when I started an experiment, so I was more than a little anxious. I have an Adaptec SCSI card (to service an HP 5p scanner); it installs a BIOS that provides 13h extensions if an HD is involved, so I got a small one, 2G Quantum Fireball, with the idea that if the extensions were installed, the larger HDs (48bit type) might then be fully visible, using Rudolph Leow's patch for ESDI506.pdr, such that a non-boot larger than 127G drive could be used, ala, sort of, XP. Rather tenuous, of course, but I was in an experimental mode. The PSU felt like an attack from the rear :-)). But I have yet to get 98 to see the SCSI disk, so I'm nowhere near the danger point actually :-D)). Again, thanks, Joe "glee" wrote in message ... After following mae's suggestions of correcting your date and time (and check your time zone too), reboot, and post back with what issues still exist. As for the OE settings for expanding threads and opening news messages, click Tools menu Options Read tab, and select them there. ...Glen, with one "n" :-) -- Glen Ventura, MS MVP Shell/User, A+ http://dts-l.org/ http://dts-l.org/goodpost.htm "et" wrote in message ... First, sorry to pile this all into one post, esp since it might best go to the OE ng, but it is more than that . . . After a PSU (rel new, 6 mos., Antec) failure last Saturday which caused no damage since it simply refused to start the next day, I found that AVG refused to load, telling me I had to upgrade to 7.5, and ZA Free wouldn't start either, saying some root certificates were probably damaged. ZA wouldn't uninst, same message, and after using Martau's TUn (old free version), it was still there, much as mentioned by, I think, Glenn Ventura in a thread some time back. I ended up weeding it all out, much as I remembered the ZL web site describes, then still found it was there (SpyBot TeaTimer told me), found the last few pieces, and then, finally found glee's post saved from that thread, with the important part of renewing the certificates, which I did--strange process, that--reloaded ZA Free (last W98 compatible version) and then downloaded the new AVG. But I decided with all this mess, I'd best uninstall the old, and install fresh. Did that, but it keeps saying the database, last updated on 11/9/06 is 1826 days old and is thus unsafe--Red flagged, etc. The icon's in the tray, but I'm not certain it's truly active, and this is suspicious, anyhow, and it makes no difference trying to update. When I tried to log on to the AVG free forum, it wouldn't accept my logon, and when they sent me a new password, it wouldn't accept that or the next one either. So no AVG forum. First thing I found was that every time I open OE under my identity, it says the server's certificate doesn't exist, but allows me to connect when I click on it. Then, I find, although it appears to be downloading new headers, it never displays them. So I set up my wife's identity to look at win98_gen_discussion and sure enough, they display. But even stranger, clicking on a header immediately displays the message in the preview pane (mine has always required spacebar or clicking on the "link" in the pane) *and* none of the threads are expanded (mine always were). I thought there was an option for that somewhere but can't find it. Anyway, the questions I'm asking are, what could cause the certificate damage like that? What sort of mechanism would cause *just* my OE identity to question the certificate for the ISP server, when it doesn't on *this* identity (my wife's). How could anything like this damage my OE identity? Does anyone know of strange AVG behavior (the update question) like that? Or the forum password difficulty? Incidentally, I think it pretty poor practice to deactivate the old version simply because they weren't supporting it anymore--would make much more sense just to warn. Mainly, I'd like to understand a little about what went on here, and how these certificates work, as this all came as something of a surprise. Malware is a *little* unlikely--I'm on dialup, and the most risky sites the machine ever visits is the comics site my wife visits to read '9 chickweed lane' every Saturday. I ran a SpyBot scan with clean results and will try some others (e.g., David Lipman's Rx) as I can find the time, but I'm hoping someone has some specific ideas on this. Apologies for the rambling length of this. Thanks, Joe (jt3) |
#4
|
|||
|
|||
Damaged Certificates, ZA free, and AVG dysfunction?
If the scsi card's bios is loading (you should see a scsi bios message
detecting scsi devices), the 2GB hard drive should be seen both in msdos and windows. Whether a scsi hard drive is connected or not has no bearing if the scsi bios is enabled. The scsi bios will load if enabled. The driver provided by Adaptec for the scsi card for your version of windows would allow 32 bit access to the said scsi hard drive. The scsi bios has no bearing to onboard ide hard drives discovered by the onboard bios. The scsi hard drive has to be partitioned and formatted, just like an ide hard drive. If the scsi bios has an asset for low-level formatting, go ahead and use that first. Then, partition and format. Such a hard drive, if adapter and hard drive are ultra or faster, is good alternative location for the swapfile. The scsi hard drive should be using scsi ID 0 or 1. The scanner a greater number of either 0 or 1. -- Jonny "jt3" wrote in message ... Thanks, Glen. (easier not to make mistakes of that sort with the example right in front, yes? Sorry about the 'n'.) As I replied to Mae, I should have thought a bit before I pushed the panic button. But a PSU failure can induce that sort of thing, I think. But I must admit that I had no idea before this happened that DUN checked the ISP server for a certificate upon connecting. Anyhow, retrospectively, 20/20 of course, it makes much sense. If I had no more trouble from the failure than a little corruption of the CMOS, I guess I'm pretty lucky. Actually, this all started when I started an experiment, so I was more than a little anxious. I have an Adaptec SCSI card (to service an HP 5p scanner); it installs a BIOS that provides 13h extensions if an HD is involved, so I got a small one, 2G Quantum Fireball, with the idea that if the extensions were installed, the larger HDs (48bit type) might then be fully visible, using Rudolph Leow's patch for ESDI506.pdr, such that a non-boot larger than 127G drive could be used, ala, sort of, XP. Rather tenuous, of course, but I was in an experimental mode. The PSU felt like an attack from the rear :-)). But I have yet to get 98 to see the SCSI disk, so I'm nowhere near the danger point actually :-D)). Again, thanks, Joe "glee" wrote in message ... After following mae's suggestions of correcting your date and time (and check your time zone too), reboot, and post back with what issues still exist. As for the OE settings for expanding threads and opening news messages, click Tools menu Options Read tab, and select them there. ...Glen, with one "n" :-) -- Glen Ventura, MS MVP Shell/User, A+ http://dts-l.org/ http://dts-l.org/goodpost.htm "et" wrote in message ... First, sorry to pile this all into one post, esp since it might best go to the OE ng, but it is more than that . . . After a PSU (rel new, 6 mos., Antec) failure last Saturday which caused no damage since it simply refused to start the next day, I found that AVG refused to load, telling me I had to upgrade to 7.5, and ZA Free wouldn't start either, saying some root certificates were probably damaged. ZA wouldn't uninst, same message, and after using Martau's TUn (old free version), it was still there, much as mentioned by, I think, Glenn Ventura in a thread some time back. I ended up weeding it all out, much as I remembered the ZL web site describes, then still found it was there (SpyBot TeaTimer told me), found the last few pieces, and then, finally found glee's post saved from that thread, with the important part of renewing the certificates, which I did--strange process, that--reloaded ZA Free (last W98 compatible version) and then downloaded the new AVG. But I decided with all this mess, I'd best uninstall the old, and install fresh. Did that, but it keeps saying the database, last updated on 11/9/06 is 1826 days old and is thus unsafe--Red flagged, etc. The icon's in the tray, but I'm not certain it's truly active, and this is suspicious, anyhow, and it makes no difference trying to update. When I tried to log on to the AVG free forum, it wouldn't accept my logon, and when they sent me a new password, it wouldn't accept that or the next one either. So no AVG forum. First thing I found was that every time I open OE under my identity, it says the server's certificate doesn't exist, but allows me to connect when I click on it. Then, I find, although it appears to be downloading new headers, it never displays them. So I set up my wife's identity to look at win98_gen_discussion and sure enough, they display. But even stranger, clicking on a header immediately displays the message in the preview pane (mine has always required spacebar or clicking on the "link" in the pane) *and* none of the threads are expanded (mine always were). I thought there was an option for that somewhere but can't find it. Anyway, the questions I'm asking are, what could cause the certificate damage like that? What sort of mechanism would cause *just* my OE identity to question the certificate for the ISP server, when it doesn't on *this* identity (my wife's). How could anything like this damage my OE identity? Does anyone know of strange AVG behavior (the update question) like that? Or the forum password difficulty? Incidentally, I think it pretty poor practice to deactivate the old version simply because they weren't supporting it anymore--would make much more sense just to warn. Mainly, I'd like to understand a little about what went on here, and how these certificates work, as this all came as something of a surprise. Malware is a *little* unlikely--I'm on dialup, and the most risky sites the machine ever visits is the comics site my wife visits to read '9 chickweed lane' every Saturday. I ran a SpyBot scan with clean results and will try some others (e.g., David Lipman's Rx) as I can find the time, but I'm hoping someone has some specific ideas on this. Apologies for the rambling length of this. Thanks, Joe (jt3) |
#5
|
|||
|
|||
Damaged Certificates, ZA free, and AVG dysfunction?
Actually, if the HD is *not* connected, the BIOS *does not* load, and a
message is provided to that effect during boot. When the HD *is* connected, the BIOS *does* load, and a message says so. This is in agreement with what Adaptec says in the small brochure that accompanied the card. I have previously both run the Adaptec surface scan and the formatting procedure provided by the Adaptec BIOS. Makes no difference to whether or not the drive show in 98. It doesn't. No matter what I seem to try. The Quantum's info decal suggests, without actually saying so, that *presence* of the 'term' jumper block provides a terminating resistance network, but a web site I found from a retailer says explicitly that termination requires jumper block removal. No matter, tried both ways, makes no difference. The Adaptec card is set to 'autoterminate' as per their instructions, so presumably it 'unterminates' the adapter when the HD is installed. I haven't yet tried explicitly setting this in the BIOS, but that's probably my next step. The odd part is that the BIOS seems to see it just as it should, but W98 doesn't. The scanner is terminated with a plug-in network, and worked just fine for a couple of years prior to trying the HD. One reason, as I suggested, that I wanted to try this, is that the Adaptec blurb says that the BIOS supplies 13h extensions for large hard disks, and while realizing that the words may not be conveying the meaning that I have been curious to discover, if the extensions are installed in the normal manner, it would be by hooking 13h and if the extensions were the same for either bus, then there would be just a chance it might work. Hence the empirical approach. Anyhow, I still would want to make the SCSI HD work, no matter whether the 13h extensions only worked on a SCSI drive or not. Thanks for your input, Joe "Jonny" wrote in message ... If the scsi card's bios is loading (you should see a scsi bios message detecting scsi devices), the 2GB hard drive should be seen both in msdos and windows. Whether a scsi hard drive is connected or not has no bearing if the scsi bios is enabled. The scsi bios will load if enabled. The driver provided by Adaptec for the scsi card for your version of windows would allow 32 bit access to the said scsi hard drive. The scsi bios has no bearing to onboard ide hard drives discovered by the onboard bios. The scsi hard drive has to be partitioned and formatted, just like an ide hard drive. If the scsi bios has an asset for low-level formatting, go ahead and use that first. Then, partition and format. Such a hard drive, if adapter and hard drive are ultra or faster, is good alternative location for the swapfile. The scsi hard drive should be using scsi ID 0 or 1. The scanner a greater number of either 0 or 1. -- Jonny "jt3" wrote in message ... Thanks, Glen. (easier not to make mistakes of that sort with the example right in front, yes? Sorry about the 'n'.) As I replied to Mae, I should have thought a bit before I pushed the panic button. But a PSU failure can induce that sort of thing, I think. But I must admit that I had no idea before this happened that DUN checked the ISP server for a certificate upon connecting. Anyhow, retrospectively, 20/20 of course, it makes much sense. If I had no more trouble from the failure than a little corruption of the CMOS, I guess I'm pretty lucky. Actually, this all started when I started an experiment, so I was more than a little anxious. I have an Adaptec SCSI card (to service an HP 5p scanner); it installs a BIOS that provides 13h extensions if an HD is involved, so I got a small one, 2G Quantum Fireball, with the idea that if the extensions were installed, the larger HDs (48bit type) might then be fully visible, using Rudolph Leow's patch for ESDI506.pdr, such that a non-boot larger than 127G drive could be used, ala, sort of, XP. Rather tenuous, of course, but I was in an experimental mode. The PSU felt like an attack from the rear :-)). But I have yet to get 98 to see the SCSI disk, so I'm nowhere near the danger point actually :-D)). Again, thanks, Joe "glee" wrote in message ... After following mae's suggestions of correcting your date and time (and check your time zone too), reboot, and post back with what issues still exist. As for the OE settings for expanding threads and opening news messages, click Tools menu Options Read tab, and select them there. ...Glen, with one "n" :-) -- Glen Ventura, MS MVP Shell/User, A+ http://dts-l.org/ http://dts-l.org/goodpost.htm "et" wrote in message ... First, sorry to pile this all into one post, esp since it might best go to the OE ng, but it is more than that . . . After a PSU (rel new, 6 mos., Antec) failure last Saturday which caused no damage since it simply refused to start the next day, I found that AVG refused to load, telling me I had to upgrade to 7.5, and ZA Free wouldn't start either, saying some root certificates were probably damaged. ZA wouldn't uninst, same message, and after using Martau's TUn (old free version), it was still there, much as mentioned by, I think, Glenn Ventura in a thread some time back. I ended up weeding it all out, much as I remembered the ZL web site describes, then still found it was there (SpyBot TeaTimer told me), found the last few pieces, and then, finally found glee's post saved from that thread, with the important part of renewing the certificates, which I did--strange process, that--reloaded ZA Free (last W98 compatible version) and then downloaded the new AVG. But I decided with all this mess, I'd best uninstall the old, and install fresh. Did that, but it keeps saying the database, last updated on 11/9/06 is 1826 days old and is thus unsafe--Red flagged, etc. The icon's in the tray, but I'm not certain it's truly active, and this is suspicious, anyhow, and it makes no difference trying to update. When I tried to log on to the AVG free forum, it wouldn't accept my logon, and when they sent me a new password, it wouldn't accept that or the next one either. So no AVG forum. First thing I found was that every time I open OE under my identity, it says the server's certificate doesn't exist, but allows me to connect when I click on it. Then, I find, although it appears to be downloading new headers, it never displays them. So I set up my wife's identity to look at win98_gen_discussion and sure enough, they display. But even stranger, clicking on a header immediately displays the message in the preview pane (mine has always required spacebar or clicking on the "link" in the pane) *and* none of the threads are expanded (mine always were). I thought there was an option for that somewhere but can't find it. Anyway, the questions I'm asking are, what could cause the certificate damage like that? What sort of mechanism would cause *just* my OE identity to question the certificate for the ISP server, when it doesn't on *this* identity (my wife's). How could anything like this damage my OE identity? Does anyone know of strange AVG behavior (the update question) like that? Or the forum password difficulty? Incidentally, I think it pretty poor practice to deactivate the old version simply because they weren't supporting it anymore--would make much more sense just to warn. Mainly, I'd like to understand a little about what went on here, and how these certificates work, as this all came as something of a surprise. Malware is a *little* unlikely--I'm on dialup, and the most risky sites the machine ever visits is the comics site my wife visits to read '9 chickweed lane' every Saturday. I ran a SpyBot scan with clean results and will try some others (e.g., David Lipman's Rx) as I can find the time, but I'm hoping someone has some specific ideas on this. Apologies for the rambling length of this. Thanks, Joe (jt3) |
#6
|
|||
|
|||
Damaged Certificates, ZA free, and AVG dysfunction?
http://www.drivesolutions.com/info/aboutbios.shtml
See 528-Mbyte Limitation http://www.drivesolutions.com/info/aboutscsi.shtml See IDs and Termination -- Jonny "jt3" wrote in message ... Actually, if the HD is *not* connected, the BIOS *does not* load, and a message is provided to that effect during boot. When the HD *is* connected, the BIOS *does* load, and a message says so. This is in agreement with what Adaptec says in the small brochure that accompanied the card. I have previously both run the Adaptec surface scan and the formatting procedure provided by the Adaptec BIOS. Makes no difference to whether or not the drive show in 98. It doesn't. No matter what I seem to try. The Quantum's info decal suggests, without actually saying so, that *presence* of the 'term' jumper block provides a terminating resistance network, but a web site I found from a retailer says explicitly that termination requires jumper block removal. No matter, tried both ways, makes no difference. The Adaptec card is set to 'autoterminate' as per their instructions, so presumably it 'unterminates' the adapter when the HD is installed. I haven't yet tried explicitly setting this in the BIOS, but that's probably my next step. The odd part is that the BIOS seems to see it just as it should, but W98 doesn't. The scanner is terminated with a plug-in network, and worked just fine for a couple of years prior to trying the HD. One reason, as I suggested, that I wanted to try this, is that the Adaptec blurb says that the BIOS supplies 13h extensions for large hard disks, and while realizing that the words may not be conveying the meaning that I have been curious to discover, if the extensions are installed in the normal manner, it would be by hooking 13h and if the extensions were the same for either bus, then there would be just a chance it might work. Hence the empirical approach. Anyhow, I still would want to make the SCSI HD work, no matter whether the 13h extensions only worked on a SCSI drive or not. Thanks for your input, Joe "Jonny" wrote in message ... If the scsi card's bios is loading (you should see a scsi bios message detecting scsi devices), the 2GB hard drive should be seen both in msdos and windows. Whether a scsi hard drive is connected or not has no bearing if the scsi bios is enabled. The scsi bios will load if enabled. The driver provided by Adaptec for the scsi card for your version of windows would allow 32 bit access to the said scsi hard drive. The scsi bios has no bearing to onboard ide hard drives discovered by the onboard bios. The scsi hard drive has to be partitioned and formatted, just like an ide hard drive. If the scsi bios has an asset for low-level formatting, go ahead and use that first. Then, partition and format. Such a hard drive, if adapter and hard drive are ultra or faster, is good alternative location for the swapfile. The scsi hard drive should be using scsi ID 0 or 1. The scanner a greater number of either 0 or 1. -- Jonny "jt3" wrote in message ... Thanks, Glen. (easier not to make mistakes of that sort with the example right in front, yes? Sorry about the 'n'.) As I replied to Mae, I should have thought a bit before I pushed the panic button. But a PSU failure can induce that sort of thing, I think. But I must admit that I had no idea before this happened that DUN checked the ISP server for a certificate upon connecting. Anyhow, retrospectively, 20/20 of course, it makes much sense. If I had no more trouble from the failure than a little corruption of the CMOS, I guess I'm pretty lucky. Actually, this all started when I started an experiment, so I was more than a little anxious. I have an Adaptec SCSI card (to service an HP 5p scanner); it installs a BIOS that provides 13h extensions if an HD is involved, so I got a small one, 2G Quantum Fireball, with the idea that if the extensions were installed, the larger HDs (48bit type) might then be fully visible, using Rudolph Leow's patch for ESDI506.pdr, such that a non-boot larger than 127G drive could be used, ala, sort of, XP. Rather tenuous, of course, but I was in an experimental mode. The PSU felt like an attack from the rear :-)). But I have yet to get 98 to see the SCSI disk, so I'm nowhere near the danger point actually :-D)). Again, thanks, Joe "glee" wrote in message ... After following mae's suggestions of correcting your date and time (and check your time zone too), reboot, and post back with what issues still exist. As for the OE settings for expanding threads and opening news messages, click Tools menu Options Read tab, and select them there. ...Glen, with one "n" :-) -- Glen Ventura, MS MVP Shell/User, A+ http://dts-l.org/ http://dts-l.org/goodpost.htm "et" wrote in message ... First, sorry to pile this all into one post, esp since it might best go to the OE ng, but it is more than that . . . After a PSU (rel new, 6 mos., Antec) failure last Saturday which caused no damage since it simply refused to start the next day, I found that AVG refused to load, telling me I had to upgrade to 7.5, and ZA Free wouldn't start either, saying some root certificates were probably damaged. ZA wouldn't uninst, same message, and after using Martau's TUn (old free version), it was still there, much as mentioned by, I think, Glenn Ventura in a thread some time back. I ended up weeding it all out, much as I remembered the ZL web site describes, then still found it was there (SpyBot TeaTimer told me), found the last few pieces, and then, finally found glee's post saved from that thread, with the important part of renewing the certificates, which I did--strange process, that--reloaded ZA Free (last W98 compatible version) and then downloaded the new AVG. But I decided with all this mess, I'd best uninstall the old, and install fresh. Did that, but it keeps saying the database, last updated on 11/9/06 is 1826 days old and is thus unsafe--Red flagged, etc. The icon's in the tray, but I'm not certain it's truly active, and this is suspicious, anyhow, and it makes no difference trying to update. When I tried to log on to the AVG free forum, it wouldn't accept my logon, and when they sent me a new password, it wouldn't accept that or the next one either. So no AVG forum. First thing I found was that every time I open OE under my identity, it says the server's certificate doesn't exist, but allows me to connect when I click on it. Then, I find, although it appears to be downloading new headers, it never displays them. So I set up my wife's identity to look at win98_gen_discussion and sure enough, they display. But even stranger, clicking on a header immediately displays the message in the preview pane (mine has always required spacebar or clicking on the "link" in the pane) *and* none of the threads are expanded (mine always were). I thought there was an option for that somewhere but can't find it. Anyway, the questions I'm asking are, what could cause the certificate damage like that? What sort of mechanism would cause *just* my OE identity to question the certificate for the ISP server, when it doesn't on *this* identity (my wife's). How could anything like this damage my OE identity? Does anyone know of strange AVG behavior (the update question) like that? Or the forum password difficulty? Incidentally, I think it pretty poor practice to deactivate the old version simply because they weren't supporting it anymore--would make much more sense just to warn. Mainly, I'd like to understand a little about what went on here, and how these certificates work, as this all came as something of a surprise. Malware is a *little* unlikely--I'm on dialup, and the most risky sites the machine ever visits is the comics site my wife visits to read '9 chickweed lane' every Saturday. I ran a SpyBot scan with clean results and will try some others (e.g., David Lipman's Rx) as I can find the time, but I'm hoping someone has some specific ideas on this. Apologies for the rambling length of this. Thanks, Joe (jt3) |
#7
|
|||
|
|||
Damaged Certificates, ZA free, and AVG dysfunction?
Again, thank you for your effort and time.
Joe "Jonny" wrote in message ... http://www.drivesolutions.com/info/aboutbios.shtml See 528-Mbyte Limitation http://www.drivesolutions.com/info/aboutscsi.shtml See IDs and Termination -- Jonny "jt3" wrote in message ... Actually, if the HD is *not* connected, the BIOS *does not* load, and a message is provided to that effect during boot. When the HD *is* connected, the BIOS *does* load, and a message says so. This is in agreement with what Adaptec says in the small brochure that accompanied the card. I have previously both run the Adaptec surface scan and the formatting procedure provided by the Adaptec BIOS. Makes no difference to whether or not the drive show in 98. It doesn't. No matter what I seem to try. The Quantum's info decal suggests, without actually saying so, that *presence* of the 'term' jumper block provides a terminating resistance network, but a web site I found from a retailer says explicitly that termination requires jumper block removal. No matter, tried both ways, makes no difference. The Adaptec card is set to 'autoterminate' as per their instructions, so presumably it 'unterminates' the adapter when the HD is installed. I haven't yet tried explicitly setting this in the BIOS, but that's probably my next step. The odd part is that the BIOS seems to see it just as it should, but W98 doesn't. The scanner is terminated with a plug-in network, and worked just fine for a couple of years prior to trying the HD. One reason, as I suggested, that I wanted to try this, is that the Adaptec blurb says that the BIOS supplies 13h extensions for large hard disks, and while realizing that the words may not be conveying the meaning that I have been curious to discover, if the extensions are installed in the normal manner, it would be by hooking 13h and if the extensions were the same for either bus, then there would be just a chance it might work. Hence the empirical approach. Anyhow, I still would want to make the SCSI HD work, no matter whether the 13h extensions only worked on a SCSI drive or not. Thanks for your input, Joe "Jonny" wrote in message ... If the scsi card's bios is loading (you should see a scsi bios message detecting scsi devices), the 2GB hard drive should be seen both in msdos and windows. Whether a scsi hard drive is connected or not has no bearing if the scsi bios is enabled. The scsi bios will load if enabled. The driver provided by Adaptec for the scsi card for your version of windows would allow 32 bit access to the said scsi hard drive. The scsi bios has no bearing to onboard ide hard drives discovered by the onboard bios. The scsi hard drive has to be partitioned and formatted, just like an ide hard drive. If the scsi bios has an asset for low-level formatting, go ahead and use that first. Then, partition and format. Such a hard drive, if adapter and hard drive are ultra or faster, is good alternative location for the swapfile. The scsi hard drive should be using scsi ID 0 or 1. The scanner a greater number of either 0 or 1. -- Jonny "jt3" wrote in message ... Thanks, Glen. (easier not to make mistakes of that sort with the example right in front, yes? Sorry about the 'n'.) As I replied to Mae, I should have thought a bit before I pushed the panic button. But a PSU failure can induce that sort of thing, I think. But I must admit that I had no idea before this happened that DUN checked the ISP server for a certificate upon connecting. Anyhow, retrospectively, 20/20 of course, it makes much sense. If I had no more trouble from the failure than a little corruption of the CMOS, I guess I'm pretty lucky. Actually, this all started when I started an experiment, so I was more than a little anxious. I have an Adaptec SCSI card (to service an HP 5p scanner); it installs a BIOS that provides 13h extensions if an HD is involved, so I got a small one, 2G Quantum Fireball, with the idea that if the extensions were installed, the larger HDs (48bit type) might then be fully visible, using Rudolph Leow's patch for ESDI506.pdr, such that a non-boot larger than 127G drive could be used, ala, sort of, XP. Rather tenuous, of course, but I was in an experimental mode. The PSU felt like an attack from the rear :-)). But I have yet to get 98 to see the SCSI disk, so I'm nowhere near the danger point actually :-D)). Again, thanks, Joe "glee" wrote in message ... After following mae's suggestions of correcting your date and time (and check your time zone too), reboot, and post back with what issues still exist. As for the OE settings for expanding threads and opening news messages, click Tools menu Options Read tab, and select them there. ...Glen, with one "n" :-) -- Glen Ventura, MS MVP Shell/User, A+ http://dts-l.org/ http://dts-l.org/goodpost.htm "et" wrote in message ... First, sorry to pile this all into one post, esp since it might best go to the OE ng, but it is more than that . . . After a PSU (rel new, 6 mos., Antec) failure last Saturday which caused no damage since it simply refused to start the next day, I found that AVG refused to load, telling me I had to upgrade to 7.5, and ZA Free wouldn't start either, saying some root certificates were probably damaged. ZA wouldn't uninst, same message, and after using Martau's TUn (old free version), it was still there, much as mentioned by, I think, Glenn Ventura in a thread some time back. I ended up weeding it all out, much as I remembered the ZL web site describes, then still found it was there (SpyBot TeaTimer told me), found the last few pieces, and then, finally found glee's post saved from that thread, with the important part of renewing the certificates, which I did--strange process, that--reloaded ZA Free (last W98 compatible version) and then downloaded the new AVG. But I decided with all this mess, I'd best uninstall the old, and install fresh. Did that, but it keeps saying the database, last updated on 11/9/06 is 1826 days old and is thus unsafe--Red flagged, etc. The icon's in the tray, but I'm not certain it's truly active, and this is suspicious, anyhow, and it makes no difference trying to update. When I tried to log on to the AVG free forum, it wouldn't accept my logon, and when they sent me a new password, it wouldn't accept that or the next one either. So no AVG forum. First thing I found was that every time I open OE under my identity, it says the server's certificate doesn't exist, but allows me to connect when I click on it. Then, I find, although it appears to be downloading new headers, it never displays them. So I set up my wife's identity to look at win98_gen_discussion and sure enough, they display. But even stranger, clicking on a header immediately displays the message in the preview pane (mine has always required spacebar or clicking on the "link" in the pane) *and* none of the threads are expanded (mine always were). I thought there was an option for that somewhere but can't find it. Anyway, the questions I'm asking are, what could cause the certificate damage like that? What sort of mechanism would cause *just* my OE identity to question the certificate for the ISP server, when it doesn't on *this* identity (my wife's). How could anything like this damage my OE identity? Does anyone know of strange AVG behavior (the update question) like that? Or the forum password difficulty? Incidentally, I think it pretty poor practice to deactivate the old version simply because they weren't supporting it anymore--would make much more sense just to warn. Mainly, I'd like to understand a little about what went on here, and how these certificates work, as this all came as something of a surprise. Malware is a *little* unlikely--I'm on dialup, and the most risky sites the machine ever visits is the comics site my wife visits to read '9 chickweed lane' every Saturday. I ran a SpyBot scan with clean results and will try some others (e.g., David Lipman's Rx) as I can find the time, but I'm hoping someone has some specific ideas on this. Apologies for the rambling length of this. Thanks, Joe (jt3) |
#8
|
|||
|
|||
well i have tried the steps and am still lost hehhe
|
#9
|
|||
|
|||
Damaged Certificates, ZA free, and AVG dysfunction?
First, sorry to pile this all into one post, esp since it might best go to
the OE ng, but it is more than that . . . After a PSU (rel new, 6 mos., Antec) failure last Saturday which caused no damage since it simply refused to start the next day, I found that AVG refused to load, telling me I had to upgrade to 7.5, and ZA Free wouldn't start either, saying some root certificates were probably damaged. ZA wouldn't uninst, same message, and after using Martau's TUn (old free version), it was still there, much as mentioned by, I think, Glenn Ventura in a thread some time back. I ended up weeding it all out, much as I remembered the ZL web site describes, then still found it was there (SpyBot TeaTimer told me), found the last few pieces, and then, finally found glee's post saved from that thread, with the important part of renewing the certificates, which I did--strange process, that--reloaded ZA Free (last W98 compatible version) and then downloaded the new AVG. But I decided with all this mess, I'd best uninstall the old, and install fresh. Did that, but it keeps saying the database, last updated on 11/9/06 is 1826 days old and is thus unsafe--Red flagged, etc. The icon's in the tray, but I'm not certain it's truly active, and this is suspicious, anyhow, and it makes no difference trying to update. When I tried to log on to the AVG free forum, it wouldn't accept my logon, and when they sent me a new password, it wouldn't accept that or the next one either. So no AVG forum. First thing I found was that every time I open OE under my identity, it says the server's certificate doesn't exist, but allows me to connect when I click on it. Then, I find, although it appears to be downloading new headers, it never displays them. So I set up my wife's identity to look at win98_gen_discussion and sure enough, they display. But even stranger, clicking on a header immediately displays the message in the preview pane (mine has always required spacebar or clicking on the "link" in the pane) *and* none of the threads are expanded (mine always were). I thought there was an option for that somewhere but can't find it. Anyway, the questions I'm asking are, what could cause the certificate damage like that? What sort of mechanism would cause *just* my OE identity to question the certificate for the ISP server, when it doesn't on *this* identity (my wife's). How could anything like this damage my OE identity? Does anyone know of strange AVG behavior (the update question) like that? Or the forum password difficulty? Incidentally, I think it pretty poor practice to deactivate the old version simply because they weren't supporting it anymore--would make much more sense just to warn. Mainly, I'd like to understand a little about what went on here, and how these certificates work, as this all came as something of a surprise. Malware is a *little* unlikely--I'm on dialup, and the most risky sites the machine ever visits is the comics site my wife visits to read '9 chickweed lane' every Saturday. I ran a SpyBot scan with clean results and will try some others (e.g., David Lipman's Rx) as I can find the time, but I'm hoping someone has some specific ideas on this. Apologies for the rambling length of this. Thanks, Joe (jt3) |
Thread Tools | |
Display Modes | |
|
|