ExcitingBooks deleted the picture that had the "coords" on it after it was posted about here.
Also, several QXs have been answered overnight. Please see the list here:
http://otp22.referata.com/wiki/(234)_222-0004#Submitted_QX
Posted: Thu Apr 17, 2014 9:53 am
Xkeeper
It's not confirmed it's a drop, no, it's just a very suspicious set of coordinates (like the prior set that led to whatever that weird card thing was).
Posted: Wed Apr 16, 2014 1:15 am
bobdamnit
Can't be on IRC right now. Can someone confirm that this is a drop? I might have someone able to retrieve this, but I hate to send them out for nothing.
I have a friend that lives in Pendleton, OR but again, no point sending them out for nothing.
(a bit industrial, I like this one! ...followed by the old classic, Theme of WORM / Hawaii song )
Also note that Message Desk picked up at the end of this recording when the call was forwarded, his phone answering was quite funny XD
The message:
Quote:
/DROP1/BOOTLOADER FOR AS36/LOC/TBD/NOTES/TBD/
/DROP2/2014 SEASON MISSION OBJECTIVES/LOC/TBD/NOTES/TBD/
/SPECIAL/PLEASE PROGRAM BOOTLOADER TO REACTIVATE AGENT SYSTEM/
Posted: Tue Apr 15, 2014 3:35 am
bobdamnit
Don't remember when, other than it was retrieved before the Library drops, but we retrieved the Astoria, Oregon drop.
User invision was kind enough to retrieve it for us.
"We are waiting on Emtanon to provide new permanent bootloader code to bypass reset button requirement. In meantime, please validate bootloader integrity. Also, if alternate desk/best?? code is available, please also try alternate best/desk?? code. It appears the watchdog is working properly so no damage will occur on testing of additional bootloader software. Expect Emtanon to provide new software within the week. Up to 7 days, however, is also possible. Stand by."
419 number dialled via Skype is still behaving oddly. Today, on dialling, I would hear this.
This is, again, a recording rather than anyone on the end of the line. So far we can't make out anything being said. The beeps at the beginning seem to be the same as the beeps from the "creepy breathing" recording a couple of days ago.
This afternoon, dialling 419 via Skype reverted to the standard Vaughnsville error message, exactly as you get when dialling via phone.
Posted: Wed Apr 09, 2014 12:29 pm
morningcoffee
Controller is now back to giving the "corrupted bootloader" prompt.
My QX was answered overnight:
"Depending on the looping or error condition, the internal watchdog will purge memory if not swatted, as long as you do not interfere with the default interrupt table. The watchdog will flush memory after time. Tier 1 support is not entirely certain why this situation is occuring. Normal watchdog timeouts consist of minutes, not hours. Standby and try upload the positional bootloaders at a later time."
(not sure about "swatted" and "positional" but that's what I heard, the "Charles" robot voice is hard to understand!)
I responded to this with a new QX, simply saying message received and understood, pointing out that controller has now returned to corrupted bootloader prompt, and asking to be kept updated with any further instructions.
Also, there's more weird behaviour from the 419 number when calling via Skype. After my UF post yesterday, my Skype was refusing to connect to the number at all. However, when I tried this morning, I found that 75% of the time Skype would return an error and not connect the call, but the rest of the time I would apparently be forwarded to a different number, most of which seem to be businesses. I was connected to a hotel, a pharmacy in Wapakoneta, Ohio, Mountain of Fire and Miracles Ministries and prayer line in Bowie, Maryland (got this twice), Net 10, a voicemail that had "not been initialised by the customer you are calling", and then after many calls, I got the "creepy breathing" recording I was getting yesterday.
This only happens when calling with Skype. Calling on an actual phone just gets the regular Vaughnsville error message.
Posted: Tue Apr 08, 2014 6:50 am
morningcoffee
A further update.
Everything seemed to be OK after the bootloader test according to the checklist. However it was decided in channel to experiment with the bootloader prompt (after the functional test, it went back to the "corrupted bootloader" prompt) and.... well, it broke, basically We don't know if it was a result of playing with it after the test, or if this was planned. On dialling, you now get the standard "agent system welcome" message ("Please enter your agent number, listed on OTP" etc) followed by an endless series of loud error-ish buzzes. It does not accept input at all.
I had responses to my QX that was left earlier immediately after the successful test.
Response: "Emtanon has requested additional question. Did controller card output error buzzer *something* upon any byte entry? If so, how many? May be indicative of memory failure. If more than one or two, bootloader programmings have failed. Results to be submitted to Emtanon within 12 hours. Unfortunately, due to a delay of test execution, Emtanon will not be ready for several days. We have requested this be expedited. Confirm this message receipt on QX and wait for response on this new QX."
Recording: http://vocaroo.com/i/s0k7vpwrr471
I left a follow-up QX stating that only confirmation chirps were heard while I was inputting the test bootloader, I did not hear any error buzzers at that time, and the functional test appeared to be successfully completed according to the checklist provided. I asked for further info.
Response: "The test plan did not include a test to ensure that the bootloader test code removes itself out of memory after execution. Please verify that prompt indicates a corrupted bootloader. Reference this QX in next reply."
Recording: http://vocaroo.com/i/s1xzUbfqUs08
I left a follow-up QX stating that the prompt had indicated corrupt bootloader immediately following the completed test, but that it was now giving agent system welcome and buzzes, and asked for further instructions.
Posted: Mon Apr 07, 2014 5:03 pm
drawbars
just wanted to upload the image from the sears catalog. the note was between these pages
Posted: Mon Apr 07, 2014 1:41 pm
morningcoffee
Progress!
After some playing around, and discussion in IRC, I dialled 888, then went to the admin menu. I pressed 3 for MXP20, and then pressed 1 to "switch MXP20 to 256 byte mode". On a hunch, I then dialled controller and attempted to enter the bootloader drawbars found at the Rhnert Park drop in its entirety. This time, I was able to enter the full bootloader without being told it was "out of memory".
On dialling again, I was given the standard agent system prompt, entered Ai's agent number, and heard a series of 3 tones, a voice read out "values", then said "complete" and played more tones - exactly as described on the bootloader checklist here: http://i.imgur.com/WrUYpPa.jpg
We've tried inputting the bootloader into Controller. I typed in 129 entries (manually... not fun) and was then told "out of memory". We're not quite sure at the moment how we're supposed to shorten it, or split it, or whatever, so that the prompt will accept it. Or if this is supposed to fail and we're supposed to report that via QX.
I noticed yesterday morning that dialling the 888 number (network services complex) is now giving a redirect to the old Vaughnsille "the number you have dialled, 646-0004, is not in service" error message - originally heard in 2012.
Dialling 419-646-0004 gives the same error message - the call doesn't connect at all. However, I found that when I dialled it on Skype (with a US Skype phone number), occasionally it would actually connect my call, and I would hear the following weirdness:
http://vocaroo.com/i/s1KEwkQGog4P
Please note that everything you hear is on the other end of the phone, including breathing, typing, and Skype message sounds. My microphone was muted.
I was able to get this when my call connected several times, but only when dialling via Skype. I believe it's a recording rather than someone actually on the other end of the line as it seems to sound the same each time. I tried pressing buttons but it didn't react to input at all.
No idea if this means anything or is just PM playing with me
This morning, 888 number is now going to the Network Services Complex again, and there's a new recorded message.
"You have reached the network services complex. Please note, minor administration orders may now be created through oh-zero-oh-four. Thank you."
It then goes to dialtone and waits for input, as normal. If you dial 0004 here, you get a menu.
"Administration menu. Press 1 for Deep Springs, press 2 for Cleveland Direct, or press 3 for MXP20".
Pressing 1 gives the message: "Press 1 to *something* up the Deep Springs link work route, or press 2 to release. Press # for more info."
Pressing # at this point: ""When not in use, the Deep Springs route may be *something* up through this routine. Please note, extended activity is NOT recommend. Routine calls may be placed through a Class 6 type (tie??) route."
A recording of pressing 1 for Deep Springs and then pressing # for "more info": http://vocaroo.com/i/s0WWT65ZEzXt
Pressing 2 got me the standard NSC "the network is currently unavailable" message.
Pressing 3 got me: "Legacy compatibility options are not currently available without assistance. Press 1 to switch MXP20 to 256 byte mode."
Recording of pressing 3: http://vocaroo.com/i/s0sADUOB7wJD