as_the_gavel_falls

Some nice items up for bid Atari 2600 Mystique Beat'em and Eat'em Complete / New in Open BOX CIB Atari CX-2689 Kangaroo for Atari 2600 NAUB Atari CX7862-849116 Atari 7800 Ikari Warriors NIB Atari CX26145 849117 Atari 2600 Venture NIB Atari CX7802 849119 Atari 7800 Asteroids NIB Atari CX7824 Atari 7800 One-On-One NIB Crushed Corner Atari CX7857 849118 Atari 7800 Jinks NIB Atari CX7805 Atari 7800 Galaga NIB Atari CX2623 849153 Atari 2600 Home Run Homerun NIB Atari CX2640 Atari 2600 RealSports Baseball NIB Atari CX2677 849144 Atari 2600 DigDug Dig Dug NIB Atari CX5218 849141 Atari 5200 Defender NIB Atari CX7834 849148 Atari 7800 Baseball NIB Atari CX7837 849146 Atari 7800 Dark Chambers NIB Atari CX7844 849143 Atari 7800 Crossbow NIB Atari CX7859 849147 Atari 7800 Barnyard Blaster NIB Atari CX7863 Atari 7800 Mat Mania Challenge NIB Atari CX7875 849142 Atari 7800 Meltdown NIB Atari CX2646 849152 Atari 2600 Pac Man PacMan NIB cellophane torn Atari CX7856 Atari 7800 Tower Toppler NIB Atari CX2688 849145 Atari 2600 Football NIB Activision Summer and Winter Games Atari 2600 PAL Box and Carts Atari 2600 Sesam, Öffne Dich / Open, Sesame! CIB PAL Quelle / Bit Corporation

Atari 2600 power supply, $1, free shipping -> https://smile.amazon.com/dp/B000IMKVCM?tag=oakmr-20 Coax adapter, $1, free shipping -> https://smile.amazon.com/dp/B0028MXN84?tag=oakmr-20 Tesa friction tape, $1, free shipping -> https://smile.amazon.com/dp/B00ZH5XOU6?tag=oakmr-20 Selling 1 of each per hour, if you can't find the $1 offer, check back in an hour. Enjoy!

Yeah, that's a pretty confusing term, sorry, I use it still as "other equipment manufacturer". I guess where I learned it, in the audio business, it generally refers to someone that makes cabinets to manufacturer spec and uses that manufacturers speakers in it, e.g. a JBL woofers and tweeters in a cabinet you make in house. "OEM (pronounced as separate letters) is short for original equipment manufacturer, which is a misleading term for a company that has a special relationship with computer producers. OEMs are manufacturers who resell another company's product under their own name and branding. While an OEM is similar to a VAR (value-added reseller), it refers specifically to the act of a company rebranding a product to its own name and offering its own warranty, support and licensing of the product. The term is really a misnomer because OEMs are not the original manufacturers; they are the customizers." I probably still didn't use it correctly.

Hi everyone, not sure how long I'll keep this price, so a good time to pick up one or two spares http://www.amazon.com/Ac-Power-Adapter-Atari-7800-System/dp/B007PE1OZY

Thanks!

What is this item?

Yep, I used to play one of these at the Payless at Rockridge shopping mall in Oakland. Remember it exactly like that, probably logged 1000 hours on one of them

I just can't believe I can't make any headway on getting ebay to take action against this huge nest of feedback fraud I discovered. They are enjoying a huge amount of profit from this network of sellers and as far as I can tell that is collusion. You can start at any the sellers, look for userids with the pattern [a-z]*[0-9][0-9][0-9]* (some letters followed by some numbers) and find many things which are obvious indicators. What makes me really sick is that these people aren't even slightly trying to hide what they are doing; one series all have 3 feedbacks from the same 3 items from the same 3 sellers at the same time, and the accounts were all registered on the same day in the UK.

The 2000 nonexistant users that all registered on the same day and are now "no longer registered users" should leave feedback first

Battlezone

Well, I thought I knew my way around ebay, but got burned for $40. "Thank you for writing eBay in regard to your further concerns. Before suspending a member, we review the member's profile and take the feedback into account. But we don't suspend members based on the feedback score alone." Look at these users, and tell me they weren't created for the sole purpose of generating fraudulent feedback. I mean, jeez, this guy isn't even trying to hide the fact these are fraudulent; half of them registered for ebay on the exact same day! You can find dozens more in this user "lazy-juicy"s profile. http://feedback.ebay.co.uk/ws/eBayISAPI.dl...al=0&page=2 http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback http://feedback.ebay.co.uk/ws/eBayISAPI.dl...tab=AllFeedback If 99% of the feedbacks are fraud, it's pretty easy to get to 99% + rating.

Great dealings, plus he lives about two miles away from me. His building is 118.7 feet by google maps from a treehouse/fort I built when I was 17

Multiple dealings both buying and selling, think I even met him in person once back in the mists of time.

There was a sweet power outage at 365 main last year. Took out craigslist, technoraiti, typepad, myspace, etc.... 365 main has n+2 redundancy that is so beautiful it makes engineers cry when we read it. There are no batteries, utility power powers a hitec UPS which has a constantly spinning 2 ton fly wheel which powers geneartors which power the building. In the event of a power failure, the diesel engines kick on and keep the flywheel spinning. The extreme techs out there may greatly enjoy this lengthly discussion of the problem and investigation. Hello, At approximately 13:53 PDT, our network monitoring tools indicated an issue with our router out of San Francisco in 365 main facility. If you are receiving this email, then one or more of your circuits is homed to this particular device in our nap. At this time, we are seeing the line protocol of the circuits in down states. We are investigating this issue, and will provide updates as they become available. ------------------ 365 Main has advised that they intend to stay on generator power for the majority of the night. They are working to ensure that utility power is 100% stable before transferring the load. We will be working with 365 Main to determine exactly what systems failed and why power was not transferred to UPS/generator as expected. An official explanation will be forthcoming. -------------------- > At 1:49 p.m. on Tuesday, July 24, 365 Main's San Francisco data center > was effected by a power surge caused when a PG&E transformer failed in > a manhole under 560 Mission St. > > An initial investigation has revealed that certain 365 Main back-up > generators did not start when the initial power surge hit the building. > On-site facility engineers responded and manually started effected > generators allowing stable power to be restored at approximately 2:34 p.m. > across the entire facility. > > As a result of the incident, continuous power was interrupted for up > to 45 mins for certain customers. We're certain colo rooms 1, 3 and 4 > were directly affected, though other colocation rooms are still being > investigated. We are currently working with Hitec, Valley Power > Systems, Cupertino Electric and PG&E to further investigate the > incident and determine the root cause. > > Utility power has been restored but all generators will continue to > operate on diesel until the root cause of the event has been > identified and corrected. Generators are currently fueled with over 4 > days of fuel and additional fuel has already been ordered. --------------------- (here's where it gets good) > UPDATE: 5:00 P.M., Wednesday, July 25, 2007 > > A complete investigation of the power incident continues with several > specialists and 365 Main employees working around the clock to address > the incident. > > Generator/Electrical Design Overview > > The San Francisco facility has ten 2.1 MW back-up generators to be > used in the event of a loss of utility. The electrical design is N+2, > meaning > 8 primary generators can successfully power the building (labeled > 1-, with 2 generators available on stand-by (labeled Back-up 1 and > Back-up > 2) in case there are any failures with the primary 8. > > Each primary generator backs-up a corresponding colocation room, with > generator 1 backing up colocation room 1, generator 2 backing up > colocation room 2, and so on. > > Series of Electrical Events > > * The following is a description of the electrical events that > took place in the San Francisco facility following the power surge on > July 24, 2007: > > o When the initial surge was detected at 1:47 p.m., the > building's electrical system attempted to roll all colocation rooms to > diesel generator power. > > o Generator 1 detected a problem in its start sequence and shut > itself down within 8-10 seconds. The cause of the start-up failure is > still under investigation though engineers have narrowed the list of > suspected components to 2-3 items. We are testing each of these > suspected components to determine if service or replacement is the > best option. Generator 1 was started manually by on-site engineers > and reestablished stable diesel power by 2:24 p.m. > > o After initial failure, Generator 1 attempted to pass its 732 > kW load to Back-up 1, which also detected a problem in its start > sequence. The exact cause of the Back-up 1 start sequence failure is > also under investigation. > > o After Generator 1 and Back-up 1 failed to carry the 732 kW, > the load was transferred to Back-up 2 which correctly accepted the > load as designed. > > o Generator 3 started up and ran for 30 seconds before it too > detected a problem in the start sequence and passed an additional 780 > kW to Back-up 2 as designed. > > o Generator 4 started up and ran for 2 seconds before detecting > a problem in the start sequence, passing its 900 kW load on to Back-up > 2. This 900kW brought the total load on Back-up 2 to over 2.4 MW, > ultimately overloading the 2.1 MW Back-up 2 unit, causing it to fail. > Generator 4 was manually started and brought back into operations at > 2:22 p.m. Generator 4 was switched to utility operations at 7:05 a.m. > on 7/25 to address an exhaust leak but is operational and available in > the event of another outage. > > o Generators 2, 5, 6, 7 and 8 all operated as designed and > carried their respective loads appropriately. > > o By 1:30 p.m. on Wednesday, July 25, after assurance from PG&E > officials that utility power had been stable for at least 18+ > continuous hours, 365 Main placed diesel engines back in standby and > switched generators 2,5,6,7, 8 to utility power. > > * Customers in colocation rooms 2, 4, 5, 6, 7 & 8 are once gain > powered by utility, and are backed up in an N+1 configuration with > Back-up 2 generator available. > > * Generators that had failed during the start-up sequence but > were performing normally after manual start (1 & 3) continue to > operate on diesel and will not be switched back to utility until the > root causes of their respective failures are corrected. > > Other Discoveries > > * In addition to previously known affected colocation rooms 1, 3 > and 4, we have discovered that several customers in colo room 7 were > affected by a 490 millisecond outage caused when the dual power input > PDUs in colo 7 experienced open circuits on both sources. A dedicated > team of engineers is currently investigating the PDU issue. > > Next Steps > > * Determine exact cause of generator start-up failure and PDU > issues through comprehensive testing methodology. > > * Replacements for all suspected components have been ordered > and are en route. > > * Continue to run generators 1 & 3 on diesel power until > automatic start-up failure root cause is corrected. > > * Continue to update customers with details of the ongoing > investigation. ------------------------ ======================================== UPDATE: 4:30 P.M., Sunday, July 29, 2007 ======================================== SUMMARY . Comprehensive testing of speed control and regulation components and their relationship to the startup sequences of the generators continues. . Unit 1 continues to be the focus of initial testing. During over 100 start/stop tests late Saturday night on Unit 1, the investigation team was able to simulate failure. The digital controller for the diesel engine (know as a DDEC) has proven erratic and a spare DDEC is en route. While this component is the focus of the investigation, the team continues start/stop testing to rule out other potential contributors to failure. CURRENT GENERATOR STATUS . Operational status is unchanged. The overall facility continues to operate at N+1 power system redundancy. Unit 1 remains offline, pending some additional testing. Unit 3 continues to support customer load in Diesel mode. All other units are supporting customer load in Normal mode. OTHER DISCOVERIES . None NEXT STEPS . Determine exact cause of diesel engine synchronization failure and PDU issue. . Continue to run generator 3 on diesel power until diesel engine synchronization failure root cause is corrected. . Continue to update customers with details of the ongoing investigation. Reports will be posted each day at 4:30 p.m. until root cause is determined. ------------------------------------ > UPDATE: 4:30 P.M., Monday, July 30, 2007 > > SUMMARY > > # The investigation team further pinpointed the digital > controller of the generator unit as the probable root cause > of failure in Unit 1. After altering the suspect DDEC > component, the investigation team was able to successfully > start Unit 1 over 60 times without incident. > > # Hitec technicians performed a series of tests that > confirmed the timing sequence for the DDEC controller was the > probable cause of the 7/24 failure-to-start event. > > # Having corrected root cause on Unit 1, the team > successfully returned Unit 1 to utility without incident and > turned testing focus to Unit 3. > Unit 3 was first powered down for inspection of the clutch > oil and proactive replacement of the clutch oil feed grommet > (the unit had been running in diesel mode for 6 days). When > the inspection and repairs were completed, the team was able > to fail the unit and observed the same error in the DDEC > component. Technicians have implemented the DDEC fix on Unit > 3 and are in the process of verifying this was the root cause > of start sequence failure on Unit 3. > > > CURRENT GENERATOR STATUS > > # Operational status has changed since the last update. Unit > 1 has finished testing and repairs and has been returned to > Normal operation supporting customer load. Customer loads > have been transferred from Unit 3 which had been operating in > Diesel mode since Tuesday. All other units continue to > support customer loads in the Normal mode. The overall power > system redundancy remains at N+1. > > > NEXT STEPS > > # Complete root cause analysis and implement fixes on all > affected generators. Return building to normal operations > once testing is complete and stability is proven. > > # Publish complete details of the investigation for 365 Main > customers. ----------------------- UPDATE: 4:30 P.M., Tuesday, July 31, 2007 SUMMARY * Generator investigation o DDEC was confirmed as root cause on each affected generator. All units have been fixed and returned to normal operation. * PDU investigation in colo 7 o The 490ms outage in colo 7 occurred at the PDU not at the generator/fly-wheel UPS (Hitec). o The PDU has 2 sources of power; primary (Source 1) and back-up (Source-2). During the power event there was a power surge on the primary (Source 1) over 11%, more than the allowable setting of the PDU device. The PDU tried to switch to the redundant (Source 2) power supply. That power supply was trying to accept the load from three other COLO rooms and reached an overload condition and did not allow the transfer. The PDU then switched back to the primary (Source 1) supply. During this time 490ms passed before the loads on the COLO 7 PDUs were put on the unit 7 generator/fly-wheel UPS (Hitec). o To correct this issue, we have set the over-voltage/under-voltage parameters to (+/-) 20% for all units in the building. PDUs performed normally following the change. 365 Main is implementing this change on all PDUs in all facilities. CURRENT GENERATOR STATUS * Following thorough testing and the successful implementation of the DDEC fix across all units, all generators are currently operating normally. The overall power system redundancy has returned to N+2. --------------------------------------

Yah, which river raid hack [font="Times New Roman"] 01b09872dcd9556427761f0ed64aa42a Galaga (19xx)(-)(NTSC)[h][River Raid].bin 03fb7cd7309c9d2678419184ecb55e75 softvision_river_raid.bin 04390ab672b01fec175920fe681094be River Rampage (2004) (Erik Mooney) (Prototype).bin 073d7aff37b7601431e4f742c36c0dc1 Bermuda (AKA River Raid) (Unknown) (PAL).bin 0c1c21d4f27e64505554d3a63b2acc88 Death Race 2000 (fixed) by neotokeo2001 (River Raid Hack).a26 1b8d35d93697450ea26ebf7ff17bd4d1 Marineflieger - River Raid II (AKA Seahawk) (1983) (Quelle) (176.764 9 - 781644) (PAL).bin 1e89f722494608d6ea15a00d99f81337 River Raid (1982) (Activision) (PAL) [p1][!].a26 291cc37604bc899e8e065c30153fc4b9 River Raid (1982) (Activision) [!].a26 304512528a5530a9361e8a231ed9a6de River Raid Plus by Thomas Jentzsch (River Raid Hack).a26 31512cdfadfd82bfb6f196e3b0fd83cd River Patrol (1984) (Tigervision) (7-004).bin 33ed6dfac4b9ea2f81f778ceddbb4a75 River Raid (1982) (SpkSoft) [t1].a26 393948436d1f4cc3192410bb918f9724 Riveraid.bin 39d36366ae7e6dfd53393fb9ebab02a0 cce_river_raid.bin 39fe316952134b1277b6a81af8e05776 River Raid (Robby) (18).bin 3ed96708c549b245599965d06ba69bb6 RiverPatrol.zip 4e86866d9cde738d1630e2e35d7288ce River Raid III (AKA River Raid) (Supergame).bin 59f596285d174233c84597dee6f34f1f River Raid (1983) (CCE).a26 65ba1a4c643d1ab44481bdddeb403827 River Raid II (AKA Katastrophen-Einsatz) (1983) (Starsoft) (PAL) [!].a26 6b57e88751bfaeaa6999b7343228e2f2 Death Race 1 (River Raid Hack).a26 6ce2110ac5dd89ab398d9452891752ab River Raid (1982) (Polyvox).a26 6d95f46ecdd6aabb412df123041515cb River Raid Black (River Raid Hack) (2005) (Scott Dayton).bin 6f6b7dbf163976ce745511501e40d135 Death Race 2000 by neotokeo2001 (River Raid Hack).a26 7a9649bbb6478fdac785605e5af1d481 Planet Raid by RetroFan (River Raid Hack).a26 7ffa5300ed3283796bd45cb5450c5f49 Planet Raid 0.9d by RetroFan (River Raid Hack).a26 8b51a3178b661cb1eb19eff361141872 Alien Menace (2005)(neotokeo2001)(NTSC)(beta)[h][River Raid].bin 8c8b15b3259e60757987ed13cdd74d41 River Raid (1984) (Supergame) (71).bin 8c941fa32c7718a10061d8c328909577 River Raid (Digivision).bin 90f502cbf4438a95f69f848cef36eb64 digitel_river_4.bin 9193b6fff6897d43274741d4f9855b6d River Raid II (AKA Katastrophen-Einsatz) (1983) (Starsoft) [f1] (NTSC).a26 927d422d6335018da469a9a07cd80390 River Raid (1982) (Activision) (PAL) [!].a26 95c4576d6a14e2debfa0fd6f6ec254ab River Raid (1982) (Activision) [a2].a26 986f1fe223de70adb1d41fa292ca7dad Death Race 1 (River Raid Hack) [a1].a26 9c40bf810f761ffc9c1b69c4647a8b84 2-in-1 - Frostbite and River Raid (Genus) (PAL-M) [p1].a26 9f17f22c9c088c3910a5162e0bd13b75 River Raid Black V2 (River Raid Hack) (2005) (Scott Dayton).bin a94528ae05dd051894e945d4d2349b3b River Raid (1983) (Genus) [p1].a26 ab56f1b2542a05bebc4fbccfc4803a38 River Raid II (1988) (Activision) [a1][!].a26 ac552f4cc3713fb91b6795aad61ef8b3 Gunfight 2600 - Red River (MP).a26 b049fc8ac50be7c2f28418817979c637 River Raid II (1988) (Activision, David Lubar) (EAK-048-04, EAK-048-04B) (PAL).bin b58bc6fca320eb6edc7b56e21aaa5637 River Raid (1982) (Activision) [t1].a26 b9232c1de494875efe1858fc8390616d Harbor Escape (AKA River Raid) (1983) (Panda) (110).bin bccb4e2cfad5efc93f6d55dc992118ce River Raid (1982) (Activision, Carol Shaw) (AX-020, AX-020-04) (8K).bin bcef7880828a391cf6b50d5a6dcef719 Bermuda (AKA River Raid) (1983) (Quelle) (322.913 5) (PAL).bin c08d0cee43077d3055febb00e5745c1d Super Hit Pak - River Raid, Grand Prix, Fishing ,Sky Jinks, Checkers (Activision) (PAL) [!].a26 c29d17eef6b0784db4586c12cb5fd454 River Raid (Hack) (2600 Screen Search Console) (Jone Yuan Telephonic Enterprise Co).bin c74bfd02c7f1877bbe712c1da5c4c194 River Raid (Tanks Hack).a26 c970b33552accd91e31d70300a7b58ba River Raid Neo (River Raid Hack) (2006) (Scott Dayton).bin cd4423bd9f0763409bae9111f888f7c2 River Raid (1982) (Jone Yuan Telephonic Enterprise Co) (NTSC by Galaga) [p1].a26 cf3c2725f736d4bcb84ad6f42de62a41 Bermuda, The (AKA River Raid) (Rainbow Vision - Suntek) (SS-009) (PAL) [a].bin d5e5b3ec074fff8976017ef121d26129 River Raid (Star Game) (003).bin d5f965c159e26a1fb49a22a47fbd1dd0 River Raid II (AKA River Raid) (Supergame).bin da5096000db5fdaa8d02db57d9367998 digitel_river_raid.bin dd92d6ad50976f881d86b52d38616118 River Raid by SpkSoft (Hack) (PAL).a26 ddc721cebcdb6d33e36fa41b6a5f3496 Planet Raid 1.0 by RetroFan (River Raid Hack).a26 de7da104cb244c42828357a94d2f2c0c Alien Menace (2005)(neotokeo2001)(NTSC)[h][!][River Raid].bin deb39482e77f984d4ce73be9fd8adabd River Raid II (1988) (Activision) [!].a26 e1b90f1e01b1a316d7bbf141525cc00e River Barron (AKA Sky Jinks) (PAL) [p1].a26 e3b4a6d09f7aba69ae1369ede3c45ab8 SI5 Kepone's Revenge (River Raid Hack).a26 e4a0b28befaaa2915df1fa01238b1e29 Gunfight 2600 - Red River (MP) [b1].a26 eb46e99ec15858f8cd8c91cef384ce09 Ground Zero (AKA River Raid) (1983) (Goliath - Hot Shot) (83-113) (PAL).bin edf69b123e06eaf8663cc78d8aeba06e River Raid by SpkSoft 98 (Hack) (PAL).a26 f2d4d6187903cac2d5ea8ed90dad120d digimax_river_raid_ii.bin f7acf289621fd2fa420ee8d7b58c6aff Death Race 2000 Version A (River Raid Hack) (2003) (Scott Dayton).bin f88749265416881942a5cdf05bb4c0c8 Planet Raid 0.9 by RetroFan (River Raid Hack).a26 fbb4f3debf48dc961b559384467f2057 River Raid III (1985) (Digitel-Brazil) [!].bin [/font]