Hello from Oklahoma

syntax

Member
Joined
Apr 13, 2022
Posts
15
Bash:
echo "Hello, World!"

My name is Ken. I've been working on IBM compatible computers since 1993 when my dad introduced me to his "portable" 8088. It had a carrying handle that would fold-in like a lunch pail, and a pop-out keyboard that revealed what was possibly a 9" amber screen... something like this. Open the top and the motherboard would be installed both vertically and diagonally. I think he had something like DOS v3 or v4 on it, as I recall him showing me how to edit files using edlin.
1740942577542.webp

At that time, my Mac Plus was still functional, so I wasn't too into his PC. A few years later, my Mac Plus was showing its age, and I drifted toward the PC. By this time, the 286 was becoming a thing of the past and the 386 was pretty popular, and the 486 was very high end. So it'd be safe to say I started with PC's using MS-DOS v5 and Windows 3.1, and I've been using PC's ever since.

Fast forward to today, Microsoft OS's have come a long way. Troubleshooting crashes is more complex in a preemptive multitasking OS, and Windows Update can throw some very cryptic error messages that doesn't mean much to your average Joe. Maybe I missed the memo, but troubleshooting Windows Update errors doesn't seem to be documented much anywhere. That brings me here.

I created this account a few years ago and forgot about it. A few weeks ago, I found a server that I manage was having problems with Windows Update rolling back on reboot. I created a new account, not knowing I already have this one. @PeterJ helped me fix the problem and that server is now up-to-date.

My live -- my career has been dedicated to computers. It's not just a 9-5 job for me. I find them fascinating and want to learn more. I need to know how to troubleshoot and fix Windows Update problems. I need to learn more about troubleshooting BSOD errors. I want to give back the help that was given to me. It's to my understanding that you're full and not accepting new students, and I'm hoping you can make an exception and find room for me. This is my first of 5 posts to get past the spam filter, so that I can send a PM to @Will Watts and @Tekno Venus, and hoping for many more posts to come.
 
Welcome Sys3.webp I helped a guy in the late 80s because it was taking overnight to run his payroll (8088) for 8 employees. I couldn't do anything to speed up the process. :cry:
 
I helped a guy in the late 80s because it was taking overnight to run his payroll (8088) for 8 employees. I couldn't do anything to speed up the process. :cry:
Haha! That reminds me of a client I used to manage when working for an MSP. They had a FoxPro database that ran from a Novell server. It was an old version of FoxPro, and we had to use another program that would slow the execution of FoxPro otherwise it'd crash.
 
Bash:
echo "Hello, World!"

My name is Ken. I've been working on IBM compatible computers since 1993 when my dad introduced me to his "portable" 8088. It had a carrying handle that would fold-in like a lunch pail, and a pop-out keyboard that revealed what was possibly a 9" amber screen... something like this. Open the top and the motherboard would be installed both vertically and diagonally. I think he had something like DOS v3 or v4 on it, as I recall him showing me how to edit files using edlin.
View attachment 117495

At that time, my Mac Plus was still functional, so I wasn't too into his PC. A few years later, my Mac Plus was showing its age, and I drifted toward the PC. By this time, the 286 was becoming a thing of the past and the 386 was pretty popular, and the 486 was very high end. So it'd be safe to say I started with PC's using MS-DOS v5 and Windows 3.1, and I've been using PC's ever since.

Fast forward to today, Microsoft OS's have come a long way. Troubleshooting crashes is more complex in a preemptive multitasking OS, and Windows Update can throw some very cryptic error messages that doesn't mean much to your average Joe. Maybe I missed the memo, but troubleshooting Windows Update errors doesn't seem to be documented much anywhere. That brings me here.

I created this account a few years ago and forgot about it. A few weeks ago, I found a server that I manage was having problems with Windows Update rolling back on reboot. I created a new account, not knowing I already have this one. @PeterJ helped me fix the problem and that server is now up-to-date.

My live -- my career has been dedicated to computers. It's not just a 9-5 job for me. I find them fascinating and want to learn more. I need to know how to troubleshoot and fix Windows Update problems. I need to learn more about troubleshooting BSOD errors. I want to give back the help that was given to me. It's to my understanding that you're full and not accepting new students, and I'm hoping you can make an exception and find room for me. This is my first of 5 posts to get past the spam filter, so that I can send a PM to @Will Watts and @Tekno Venus, and hoping for many more posts to come.
Welcome to sysnative community
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top