02-14-2018, 05:17 PM
(This post was last modified: 02-14-2018, 05:18 PM by DerVVulfman.)
It gets better.
The time is now 11:07am this Wednesday... roughly one week since the problems began.
Monday night, after I left the IRC room (or make that Tuesday Morning as it was past Midnight), I ventured into another forum. I was making a post to tell someone that he needed to be more specific when giving an error report (sigh... noobs). It was right then (1:15am) that I was disconnected and the same error message popped up.
Stubborn as I was, I tried reconnecting and got a NEW error message. So, I decided to call AOL once again.
Oh, my gawd. I got the same ORIGINAL phone support rep thatI talked to the night before last.... the guy who sounded like Petty Prank's 'SAM'
He informed me that the servers were still being worked on... *Yikes?* I told him of the new error code, and he appreciated the new information and was going to relay that information immediately to the tech guys.
Now let's see how long it stays up this time.
The time is now 11:07am this Wednesday... roughly one week since the problems began.
Monday night, after I left the IRC room (or make that Tuesday Morning as it was past Midnight), I ventured into another forum. I was making a post to tell someone that he needed to be more specific when giving an error report (sigh... noobs). It was right then (1:15am) that I was disconnected and the same error message popped up.
Stubborn as I was, I tried reconnecting and got a NEW error message. So, I decided to call AOL once again.
Oh, my gawd. I got the same ORIGINAL phone support rep thatI talked to the night before last.... the guy who sounded like Petty Prank's 'SAM'
He informed me that the servers were still being worked on... *Yikes?* I told him of the new error code, and he appreciated the new information and was going to relay that information immediately to the tech guys.
Now let's see how long it stays up this time.