Ideas for UMDK MD hardware support Wiki page

30 views
Skip to first unread message

csmith

unread,
Mar 26, 2017, 2:36:45 PM3/26/17
to umdkv...@googlegroups.com
Hello,

first of all: bare with me as I have an inflamed right wrist which makes
it painful for me to type much.

I need a list of all the MD hardware that needs to be added to the Wiki
for UMDK MD HW support on ZF.

Any ideas for fields and layout would help too.

I have installed Media Wiki but just need to learn about how to secure
it from spammers and such.

Cheers,

Chris.

csmith

unread,
Mar 26, 2017, 2:42:22 PM3/26/17
to umdkv...@googlegroups.com
To add:

There will sections for MD1, MD2 and MD3 for now.

csmith

unread,
Mar 26, 2017, 3:40:12 PM3/26/17
to umdkv...@googlegroups.com
I have not added in all the sections yet (wrist is killing me tonight)
but here is an idea:

https://zako-factory.org/mw28/index.php?title=UMDK_Megadrive_Hardware_Support_Page

I will link it to the main page's menu once I am happy that it is secure.

Comments and ideas let me know.

Chris McClelland

unread,
Mar 26, 2017, 5:52:01 PM3/26/17
to umdkv...@googlegroups.com
Hmmm...it seems like MediaWiki will suffer the same problems that GitHub MarkDown has. When the table gets very large, it will be next to impossible to work out what's going on. Maybe we should just use Matt's Google sheet: https://docs.google.com/spreadsheets/d/1_ylZQYq66COgB-HraOJ2wt8OExrPcUwWc-cZ-BGDIGs/edit#gid=0

He can give write access to anyone with a Google account, and it's much easier to edit than a wiki table.

Can we host ROMs somewhere and put download links in the Google sheet?

I have a feeling the signal integrity problems we've seen (from the FPGA logic-analyzer traces Montserrat grabbed, and presumably the same thing causing problems with some of Matt's consoles) is not due to board revisions, console models, etc[1], but is down to some kind of degradation of the hardware with age: the PSU caps, the VDP signal-drivers, etc. I'd like to get my hands on an incompatible console to see if I can make it work by recapping it, bypassing the regulator and using a bench supply, etc.

Chris

[1]After all, there is no clear pattern: Matt's VA6s fail, but Tasos's works. My MD2 works, Matt's fails.


--
You received this message because you are subscribed to the Google Groups "UMDKv2 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to umdkv2-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Matt Phillips

unread,
Mar 27, 2017, 5:29:13 AM3/27/17
to UMDKv2 Developers
Yup, I can tidy up the sheet, allow write access, and host the ROMs somewhere (with quick instructions of what I tested and what problems I looked for). I'll sort it when I'm home from work this evening.

Chris McClelland

unread,
Mar 27, 2017, 2:37:00 PM3/27/17
to umdkv...@googlegroups.com
The other thing that would be really helpful as a sanity-check is to ensure the sigtest passes on all your machines. That will effectively eliminate any connectivity issues.


csmith

unread,
Mar 27, 2017, 3:17:01 PM3/27/17
to umdkv...@googlegroups.com
I can host the ROMs on ZF as we have loads of space and we are all paid
for the next couple of years at the very least.

Matt Phillips

unread,
Mar 27, 2017, 3:48:55 PM3/27/17
to UMDKv2 Developers
I'll redo the sigtest on everything this weekend


On Sunday, 26 March 2017 19:36:45 UTC+1, mintythecat wrote:
Reply all
Reply to author
Forward
0 new messages