glnz

Member
  • Content count

    238
  • Joined

  • Last visited

  • Days Won

    2

glnz last won the day on August 20 2016

glnz had the most liked content!

Community Reputation

20 Excellent

About glnz

  • Birthday

Profile Information

  • OS
    XP Pro x86
  • Country
  1. Hey Heinoganda and maybe harkaz ? -- I still use your Cert_Updater.exe from time to time on my XP. (By the way, its Modified Date is 2-16-16, so I hope it's still good.) Please take a look at this article on ArsTehnica: http://arstechnica.com/security/2017/01/already-on-probation-symantec-issues-more-illegit-https-certificates/ Given the dates in the article for the bad TLS certificates and the dates I see when I run Cert_Updater.exe (some 2015 and some Nov 2016), I don't think that Cert_Updater.exe is protecting against the bad TLS certificates in the Ars article. What do you think? Happy Trump New Year, and thanks again!
  2. Dear Mathwiz - I just realized your post above at [Link to comment=1133576] quoted my post of a year ago. I still have the install file WindowsXP-KB955704-x86-ENU.exe . It's 3,324 KB. I put it in my OneDrive - try this OneDrive link - https://1drv.ms/u/s!ArpWuno4XUAMgRgqMK0ndGBrBv58
  3. I ask the title question because Ask Woody is still at defcon 2. What do you all think? Woops - I'm in the wrong topic. Am I able to move this to Win 7?
  4. Penpals everywhere - all 9 are good. Merry Christmas and Happy New Year !!!
  5. heinoganda and dencorso - thanks. heinoganda - you wrote "Make sure the MSI 4.5 (KB942288-v3) is installed!". Sorry, how do I do that? If it's not installed, what should I do? And you are right about svchost.exe - it ran 50% of my CPU for a long time last night, but I let it go. It's not doing that now. It seems that XP is finally becoming more vulnerable, now that POS is no longer included in certain .NET updates or mrt. I no longer do any banking or similar on mine. In my neighborhood in NYC, a very nice houseware and hardware store suddenly closed - Gracious Home. It's the only place I know personally that used XP POS terminals. Maybe our days are numbered.
  6. Ok, penpals who speak English, French, Portuguese, Spanish, Italian, Catalan, German, Japanese and Esperanto -- I count nine (9) updates, including a few for Office 2003+2007. Before I try, are there any 재해 災難 взрывы or ריחות רעים ??
  7. XP fans - little by little the usability of my trusty XP Optiplex 755 is whittled away. The most recent loss was the free 5GB of Cubby, which I used both (a) to back up and (b) to sync across some different PCs a bunch of small business files. In turn, Cubby had replaced the free 5GB of SugarSync. Both gone. So, what should I use for free that will both back up designated folders AND sync them across a bunch of different PCs, starting with folders on my XP but syncing them with the same folders on a few Win 7s? The nice thing about Cubby and (before that) SugarSync was that all I needed to do was right-click the folder (wherever it is) and designate it to start backing up/syncing in the program. No need to move the folder into a fake "drive". And even in a fake "drive" like OneDrive, it just won't run on XP. I know this is off-topic a bit, so please just point me in right direction. Or soon these machines will just be attractive table ornaments. Thanks.
  8. Today, in my Optiplex 780 Desktop with Win 7 Pro 64-bit and 8GB RAM, I cloned my hard drive from old drive to new drive. To do that, I went into BIOS (which is the A14 version), went to Drives, enabled SATA2, and plugged the new empty hard drive into the SATA2 socket on the motherboard. The original drive has always been in the SATA0 socket, and the CD-DVD has always been in the SATA1 socket. The clone went well (using Macrium Reflect Free in a USB stick). When I took out the old drive and connected the new cloned drive to the original SATA0 socket, the Optiplex gave me errors on the reboot. It said it was missing a drive in SATA2 and did i want to Continue, go into System or run Diagnostics. After a few reboots with that error, I went back into BIOS - Drives and disabled SATA2. Then reboot went very well without errors, a few times. All good. However, those errors aren't right. I should be able to enable SATA2 in BIOS and not get errors just because no actual drive is plugged into the SATA2 socket on the motherboard. (That's how it works in a different Dell Optiplex 3010 I have). So what's going on? Why am I getting this error? (By the way, the old drive was a 10-year old Maxtor 500GB, and the new drive is a Seagate Firecuda ST1000DX002. Do you think the SATA2 socket fell so in love with the Firecuda that it just can't let go?) Thanks. \ /
  9. SD73 - Eleven? I'm envious. What is the 11th?
  10. Ten updates (including for Office 2003-7). So, who's going first? (Not me - water's too cold.)
  11. Sherylinrm and jaclaz - unfortunately, the XP machine with the Seagate HD-SSD glitched again yesterday - it froze. (Did not see whether it was also a BSOD - probably not because BlueScreenView doesn't show anything from yesterday.) I think you're right about the Hard Drive. Too bad, as the machine's original Western Digital Velociraptor HD was nice (10,000 RPM). Since this HD is a hybrid HD-SSD, will cloning software like Aomei Backupper or Macrium Reflect have any difficulty "reading" everything on the drive and then "restoring" to a normal (NON-hybrid) HD? By the way, when I first "backed up" from the Velociraptor and "restored" into this Seagate a year ago using Aomei, I needed to recreate its bootability using my Macrium CD - it wasn't booting. But that went well. One last question - do you think it might be TeamViewer causing my HD to freeze? Is it possible that the latest versions of TV don't like XP?
  12. EDITED - FOUND REPORTS For the second time this past week, an Avast Boot-Time scan has some odd error messages but its "Scan History" says there were NO bad files. See my post on the Avast forum at https://forum.avast.com/index.php?topic=192475.0 . (<-- You might have to try the link twice to get to my thread.) Any thought whether the error messages are linked to the freezes the last two months and my two BSODs? (The Boot-Time scan meant I rebooted, but still no new BSODs or freezes last 48 hours.)
  13. drugwash - Ran memtest and also the Diagnostics boot option in my Dell (selected after F12). All good - no errors with my CPU or RAM. Thanks for suggestion.
  14. Dave-H - Thanks for the link to Nirsoft's bluescreenview. It let me see that there WAS a cause to the latest BSOD - namely mbam.sys with a STOP 0x00000019. Yes, it was running in the tray (and I have since UNchecked it as a startup item, so it's not running now). Should I upload here anything from bluescreenview? Does it reveal confidential info? Drugwash - I might try AFT later. By the way, so far almost 24 hours no BSOD and no freeze when I try to access using Teamviewer (which I'm doing now). Thanks.
  15. OK - OK - I get it! Jeez - talk about touchy! The first of my two recent BSODs blamed aswsp.sys with a STOP 0x00000050. That's an Avast file for its own software protection. The second BSOD yesterday didn't blame any file at all, and I did not shoot a photo of it. (I remember a lovely shade of blue and a lot of white letters that reminded me of clouds or soft, fluffy cotton.) There was nothing useful in Event Viewer. I suppose I could look for a minidump file and maybe attach it here? (What's its exact file name, and where is it likely to be in XP?) On one of my recent reboots the last 48 hours after starting to fiddle with msconfig, I saw that Avast was off, so I Repaired it. I set msconfig to full "Normal" after that, and that's how it's been going since. No BSODs since. Yes, a bunch of .sys lines in the ntbtlog are from third party software I've installed over the last 30 years. From your posts here, sounds like those .sys entries aren't so important. One service I shut off the last 24 hours after going to full Normal on msconfig was related to Aomei Backupper - its automatic scheduler, which I never set and never used. So, even with all the .sys lines, after I'm completely booted up and have a coffee, I have 2.6± GB showing as available RAM (from 4GB installed), which is pretty good. Well, let's see whether I get any more BSODs or freezes. I forgot to say at the beginning -- Before I got these two BSODs, my PC has been freezing about once per day the past month or so, requiring a manual reboot. Again, nothing interesting in Event Viewer. (I frequently access this PC from my work office using TeamViewer - to check on private emails at home. The past month or so, about once per day, this PC has shown in the TV list but then won't connect and then drops off the list.) Well, now that I'm using Normal in msconfig, let's see if that continues as well. Cheers!