Whelp, it turns out that my SNES is indeed a 1-chip. I’m getting the 2/1/3 for the CPU/PPU1/PPU2. My console has a serial of UN2########### though which is why I assumed it was not a 1-chip.
That said, I wonder why I’m getting the blur in FFIII. (aka FFVI)
I never played FFIII enough back in the day to know if that is normal.
If you’d read the newsletter, only those who ordered on August 26th and have been contacted are part of the 100 that are being pushed off to the next batch.
Also, if I remember correctly, he can only manage to send out about 50 OSSCs a day since he has to pack, label and ship them all himself.
I apologize, I was thinking that others were saying that those who ordered a PSU would be pushed to the 100 OSSC shortage and onto the next batch.
I ordered an OSSC way back on July 12th with a PSU added. I really wish I was given the option to get the money back and pointed to something on Amazon that could power the OSSC. I do not want to wait until December for something that was slated to be shipped in 90 days, at the worst. (I ordered prior to that change being made to the order form.)
I’ve got a number of retro systems sitting around waiting for this device to come in. It is really annoying that it seems as though because the PSUs aren’t coming in, that you’re screwing over those who decided to order one by sending them to those who ordered well after we did.
That was quoted as “The worst case scenario”, not the actual date when they’d be ready.
Considering that you’ve said that production is going along fine on the 21st, and now that the kits are for sale along with the PCBs arriving, people are wondering if you had a better/newer estimate on when the OSSCs would arrive for shipment. (Even if it is only for the earlier batch)
I think he meant a quoted time.
Both I/O and N/M are keys next to one another on a QWERTY keyboard.
| Cookie | Duration | Description |
|---|---|---|
| _gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
| Cookie | Duration | Description |
|---|---|---|
| __gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| Cookie | Duration | Description |
|---|---|---|
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| Cookie | Duration | Description |
|---|---|---|
| ct_checked_emails | session | No description |
| ct_has_scrolled | session | No description |
| ct_mouse_moved | session | No description |
| ct_screen_info | session | No description |
| wordpress_apbct_antibot | session | No description |
| wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |
