I had done from the tracks of VDP before but the Jailbar effect got worse. Soldering on the legs of the VDP is one of the best ways to avoid interference from motherboard and it’s okay to do if you recreate The three 5.6k pull-up resistor circuit like I did. All this is documented in the links:
https://www.retroorgb.com/genesisrgbbypass.html
https://www.retroorgb.com/fix-for-all-rgb-bypassed-sega-genesis.html
The point is that even I know I already done, I cut the RGB and Sync tracks that come out of the encoder to avoid interference too but my megadrive still has a number of jailbars in gray colors. I have another Japanese mega drive 1 also with the same VA1 motherboard and exactly the same RGB work which is almost perfect with very very minimal Jailbars. I don’t understand why this particular mega drive is not jailbar-free. I would like to know if anyone else has any ideas for me to further reduce this plague of Jailbars because everything I know I’ve already done. I read something about regulating the memory clock but I don’t know exactly what it is. I would like to know if anyone else has any ideas.
If it’s the voltage regulator that’s too bad because besides I don’t have the original voltage regulator anymore, the original audio DAC chip (U6) was replaced with a CS4338-KSZ chip that is housed on top of one of the screw holes of the Heatsink, making it impossible for me to install heatsink again.
If this small interference is really due to the OKI-78SR5 murata voltage regulator and there is no other way to solve this problem, maybe I just accept it and leave with that. It’s very very discreet anyway
No, I just have the original Nintendo Power supply, do you think another is better?
PS: The original voltage regulator is replace with a modern Murata OKI-78SR5
| 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 |
