Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: How many roms/bioses/ect are currently in mame? (Programmer's help needed)  (Read 4913 times)

0 Members and 1 Guest are viewing this topic.

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:Yesterday at 02:45:49 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Ok so After 17 years I think mame finally broke a few of my ancient vb6 programs.  I was getting ready to overhaul the software on my old mame cab so I ran DK's good old listgen.... except nothing happened.   It turns out that, unless I have a bug or something in my code, mame's listxml entry size has exceeded 33,000, causing my signed integers to go nuts.  I'm just wondering how big it's gotten and if it might be time for me to throw it away and start from scratch.  Obviously I can use larger variables, but if the size is super large it might just be time to try some other method. 

Perhaps MAME and MESS should split if only so the listxml is a reasonable size?

keilmillerjr

  • Trade Count: (+5)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1847
  • Last login:October 06, 2023, 10:20:39 pm
  • Web Developer.
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #1 on: February 05, 2017, 10:40:10 pm »
Maybe its time to move away from xml and go with a database like sqlite?

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:Yesterday at 02:45:49 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #2 on: February 05, 2017, 11:22:22 pm »
Honestly I don't understand why it doesn't just use a comma delimited text file.  That would be the smallest possible file size and I can't think of a database type or programming language that doesn't fully support loading a database from a delimited text file.  I mean sure there are some issues like mame allowing multiple rom entries for a single game, ect, but if it were designed properly it would work well.

I looked at the size and it's a couple of thousand over, which isn't terrible, but man, that is going to break a lot of older stuff.  If other programmers are like me they used integers (or equivalent) because in programming school they teach us to use the smallest possible variable at all times and nobody expected mame to jump past that signed integer limit of 32k.  What's worse is a lot of objects in vs6 have counting properties that are signed integer based, so yeah, they won't work. 

I mean there are workarounds, I'm probably going to filter off E.M. games as I read the xml in, but this is just ridiculous.  For a documentation project mame sure has jumped off the rails with the catalog, which you know, is part of the documentation. 

Btw understand that it has probably been this way for a while.  I kind of put mame aside for a while when I realized the direction it was going.

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:Yesterday at 02:45:49 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #3 on: February 06, 2017, 01:03:11 am »
*update*

It looks like the "device" additions in mame are what bumps the number up.  It used to be that a whole game was a device.  Now if that game has a ticket dispenser, that's a separate device and nonsense like that.  Normally I love compartmentalization, but this is a bit excessive.   

B2K24

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 216
  • Last login:June 10, 2025, 10:17:56 am
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #4 on: February 06, 2017, 01:29:59 am »
QMC2 lists 37,179 in latest baseline MAME

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:Yesterday at 02:45:49 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #5 on: February 06, 2017, 01:53:31 am »
Yeah and after I filtered off all the crap it's a mere 9759, clones and broken drivers included.  There could be errors in there as I haven't proof read the list I generated, but when 20k of the entries are unplayable it might be time to reevaluate the project's direction.  I dunno, it's just that managing mame used to be a lot easier. 

I'll release my listgen once I update my cabinet.  It outputs a delimited text file so maybe it can be useful for other frontends/projects, ect.

headkaze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2943
  • Last login:August 14, 2023, 02:00:48 am
  • 0x2b|~0x2b?
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #6 on: February 06, 2017, 04:22:56 pm »
In MAME 0180 I have 2655 after filtering all the crap out.

Haze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1296
  • Last login:October 04, 2023, 08:30:02 am
  • I want to build my own arcade controls!
    • MAME Development Blog
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #7 on: February 06, 2017, 07:20:01 pm »
Yeah and after I filtered off all the crap it's a mere 9759, clones and broken drivers included.  There could be errors in there as I haven't proof read the list I generated, but when 20k of the entries are unplayable it might be time to reevaluate the project's direction.  I dunno, it's just that managing mame used to be a lot easier. 

I'll release my listgen once I update my cabinet.  It outputs a delimited text file so maybe it can be useful for other frontends/projects, ect.

or maybe it's time you reevaluate what your opinion on what you think MAME is.

just seems that over the years, while we've consistently stated that it's not just about playing games other people have shouted down at us that we're lying, and that it is.

now that it's becoming more and more clear that we weren't lying people seem to have a hard time accepting it.

it broke your program, happens all the time, progress is progress, limitations in other software get exposed.


Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:Yesterday at 02:45:49 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #8 on: February 06, 2017, 08:03:14 pm »
Headkaze:  I haven't filtered off clones or preliminary drivers yet.  It'll get smaller, I'm just being generous with the numbers to give the project the benefit of the doubt.

And right on cue comes Haze preaching a gospel nobody believes in.  You left mame dude, it isn't your place to chime in anymore. 

If it's about playing games the project is going in the wrong direction.  If it's about documentation it is STILL going in the wrong direction.  At this point MAME reminds me of those episodes of American Pickers where they run across some guy that has a couple hundred rocking chairs rotting in a leaky barn and his excuse for keeping them is "I'm going to open a museum someday".  Well no you aren't because your stuff isn't taken care of, nor is it organized, researched, or properly documented.  Face it, MAME is hoarding drivers at this point, which would be great if the proper documentation was hoarded with them.  A game pcb is only a portion of the puzzle.  You have the cabinet, the artwork, the promotional materials, ect, ect.  Mame ignores all of that.  Heck it can't even be bothered to classify the type of game/machine/whatever a device is in the listxml.  No, it isn't difficult to classify games either... I'm sure anyone, if they have access to the info, can tell if a game is a home console, a pc, a electro mechanical game, a pinball game, an arcade game or a hybrid.  The thing is, the user doesn't have access to that info.  They just have a huge blob of over 30,000 drivers that they are supposed to know what they are ahead of time.  It's ridiculous.

No, this isn't progress.  Progress would result in a better end product.

Haze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1296
  • Last login:October 04, 2023, 08:30:02 am
  • I want to build my own arcade controls!
    • MAME Development Blog
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #9 on: February 06, 2017, 08:21:51 pm »
all you're doing is showing you have no idea what MAME is.

it's emulation software, it emulates things.  some of those things work, some of them don't.  not up to the team to decide what is / isn't worthy, only if it was a real thing or not.  It is up to people, including the team members to contribute improvements where they can to improve the emulation of those things.  Over the last couple of years we've seen people pick up some really interesting little bits and pieces that they're interested in and improve them, others haven't had that attention yet.

that's all it comes down to.

funny you scream "nobody believes in" just as you screamed "it's only about the games" I guess one day it will actually be clear.  Seems plenty of people believe in it to me, actually outside of some rather closed-minded circles I guess it is clear already and greatly appreciated.

take the recent 68705 work Vas did, now it's not only used to emulate a bunch of Taito (and other manufacturers) games but also at a level where the entire programming process for the MCU family can be emulated, that's progress, and yes, it belongs right there with the rest of the code that uses it.  Emulating things at that kind of level can also unlock many secrets about the chips, which ends up coming in handy too.
« Last Edit: February 06, 2017, 08:49:58 pm by Haze »

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:Yesterday at 02:45:49 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #10 on: February 06, 2017, 11:59:26 pm »
I'm trying to be civil so please do not insult my intelligence.  I know EXACTLY what mame is.  It's you who have, over the course of your regime,  tried to distort it into something that it isn't. 

Yeah I get it, there are a lot of chips emulated in mame.  And?  What is your point exactly?  Because there is a lot of stuff you have no obligation to DOCUMENT AND CATALOG that stuff?  I mean mame roms aren't even in readable names, they are stuck to some 8.3 file extension left over from fat stuff.  If I purposefully set out to make a program as user unfriendly as possible I don't think I would do as good a job as mame is in it's current state. 

You have 20,000 drivers that are junk, that while fascinating at the chip level, is completely unplayable and will most likely never be playable.  So why is it on the game list?  You can't claim it to be for the user, because, as I've already pointed out in numerous posts over the last few years, mame is a library without a card catalog.  There was a time in mame's history when unplayable devices were blocked from view.  I think it's time to go back to that, or either switch to something other than xml, which isn't designed to handle massive amounts of data.  Btw, I warned you guys about that when you first made the switch.  I'm usually right about that sort of thing.

Why aren't different types of devices categorized?  It would take one extra line in the xml.  Please don't reply with that nonsense about it being the same at the driver level.  Yes we all know that but seeing as we are all normal humans we know that while internally something might be alike, the end product is usually wildly different.  If you want to be silly a million things used z80 chips back in the day, but nobody in their right mind would put an automated coffee machine in the same list as a Colecovision without some kind of note that one is a coffee machine and one is a game console. 

You seem obsessed with the pcbs and chips and yet you can't seem to admit that it is pointless to document that sort of thing without documenting the entire device.  This is byoac, a site created for the very purpose of filling in one of the gaps that mame can't, namely the physical controls.  If you can't see the worth in that, and the importance of linking all the other information besides just the chips, then perhaps you don't belong here.  I mean I rarely see you post anything unless it's to contradict me. 

Haze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1296
  • Last login:October 04, 2023, 08:30:02 am
  • I want to build my own arcade controls!
    • MAME Development Blog
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #11 on: February 07, 2017, 08:08:19 am »
I'm trying to be civil so please do not insult my intelligence.  I know EXACTLY what mame is.  It's you who have, over the course of your regime,  tried to distort it into something that it isn't. 

You *clearly* don't, and even if you think you did, things evolve.  Arcade emulation is a dead end, arcade emulation is not what keeps the project alive, and hasn't been for a long, long time, it's everything else, the things you seem to hate.

Quote
Yeah I get it, there are a lot of chips emulated in mame.  And?  What is your point exactly?  Because there is a lot of stuff you have no obligation to DOCUMENT AND CATALOG that stuff?  I mean mame roms aren't even in readable names, they are stuck to some 8.3 file extension left over from fat stuff.  If I purposefully set out to make a program as user unfriendly as possible I don't think I would do as good a job as mame is in it's current state. 

You have 20,000 drivers that are junk, that while fascinating at the chip level, is completely unplayable and will most likely never be playable.  So why is it on the game list?  You can't claim it to be for the user, because, as I've already pointed out in numerous posts over the last few years, mame is a library without a card catalog.  There was a time in mame's history when unplayable devices were blocked from view.  I think it's time to go back to that, or either switch to something other than xml, which isn't designed to handle massive amounts of data.

It's a machine / item list, not a game list.  If you have that machine / item you'll know what it is.  If you dump the rom from a machine / item you don't know what is, MAME will likely be able to identify it and point you in the direction of what it is, at which point you do you can start researching it based on what MAME knows, and whatever else you can find.

Yes, there was a time when non-working stuff was disabled, and you know what, reversing that policy opened MAME up to so many more people, allowing development to be where it is today.  Almost every dev working on the project today got their chance to because non-working stuff was enabled, roms were included as part of the romset, and there were no barriers.  It's probably the single most important thing that happened to MAME because it opened it up for everybody to work on rather than anybody who wanted to look at a non-working driver having to jump through hoops just to get the ROMs that were being kept hidden from the public in a way that seemed nothing short of elitist at the time.  I guess the irony is people were complaining a LOT about the old policy back in the day, and it's one of the cases where they actually had a point.

Quote
Btw, I warned you guys about that when you first made the switch.  I'm usually right about that sort of thing.

It broke your software, nothing else, this level of ego is hilarious.  Warned us? Usually right? sorry, I see no evidence for this aside from you trying to use breakage in your program to make a false point, maybe you should have been warned or had the foresight to see that using a signed 16-bit number wasn't a good idea, I mean, it's a list, it can't have a negative number of entries in the first place.  Of course, it's old software, mistakes like that get made sometimes, it happens, I'm not going to say MAME hasn't had more stupid bugs because it has, and they've been fixed, why do you think we always recommend the latest versions?

Quote
Why aren't different types of devices categorized?  It would take one extra line in the xml.  Please don't reply with that nonsense about it being the same at the driver level.  Yes we all know that but seeing as we are all normal humans we know that while internally something might be alike, the end product is usually wildly different.  If you want to be silly a million things used z80 chips back in the day, but nobody in their right mind would put an automated coffee machine in the same list as a Colecovision without some kind of note that one is a coffee machine and one is a game console. 

If you have the machine you know what it is.   I think it's fine putting them in the same list, it's a list of machines MAME can, to some degree, emulate.  It isn't a list of games, maybe it used to be mostly games, but even then, there were things in the list that were not games (Deco Test Tape for example) and eventually the terminology was corrected to reflect that.  The test tape was added in 0.37 beta 13, released in 2001, that's at least 16 years of MAME doing non-games, only for 4 years was it exclusively games.  Things have continued to evolve past that as part of the natural progression, the most recent ones of course being the official introduction of the code from MESS because that's where most of the development actually taking MAME forward was coming from.

Quote
You seem obsessed with the pcbs and chips and yet you can't seem to admit that it is pointless to document that sort of thing without documenting the entire device.  This is byoac, a site created for the very purpose of filling in one of the gaps that mame can't, namely the physical controls.  If you can't see the worth in that, and the importance of linking all the other information besides just the chips, then perhaps you don't belong here.  I mean I rarely see you post anything unless it's to contradict me.

I'm saying MAME is *part* of that, it provides the emulation side of things, what people build and document *around* that emulation is up to them.  MAME is the engine, MAME is the technology.

What annoys me are these basically xenophobic rants from people who seem to think that MAME shouldn't do anything outside of their field of interest, or telling people that MAME is something that fits with their outdated views rather than accepting what the project actually is, or the benefits it actually has, and yes, I use the word xenophobic intentionally because the parallels are very real.  So no, we're not going to "Make MAME great again" by building an artificial wall between the types of system and putting everything on specific lists so that people can exclude them.
« Last Edit: February 07, 2017, 08:45:19 am by Haze »

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1543
  • Last login:July 15, 2025, 03:41:34 pm
  • retro maniac
Re: How many roms/bioses/ect are currently in mame? (Programmer's help needed)
« Reply #12 on: February 08, 2017, 05:10:08 am »
List of support files with BIOSes (500 files) for 182 GIT (day ago):

Code: [Select]
22vp931
3c505
3dobios
a1200kbd_rb
a1cass
a2091
a2ap16
a2ap16a
a2aplcrd
a2cffa02
a2cffa2
a2corvus
a2diskii
a2diskiing
a2hsscsi
a2iwm_flop
a2memexp
a2mouse
a2pic
a2ramfac
a2scsi
a2ssc
a2swyft
a2thunpl
a2tmstho
a2ultrme
a2ulttrm
a2vidtrm
a2vtc1
a2vtc2
a2vulcan
a2vulgld
a2zipdrv
a3fdc
a500_kbd_ch
a500_kbd_de
a500_kbd_dk
a500_kbd_es
a500_kbd_fr
a500_kbd_gb
a500_kbd_it
a500_kbd_no
a500_kbd_se
a500_kbd_us
a590
abc1600mac
abc1600mover
abc55
abc77
abc800kb
abc830
abc832
abc834
abc838
abc99
abcsio
abc_fd2
abc_hdc
abc_mem
adam_ddp
adam_fdc
adam_kb
adam_prn
adam_spi
aga
aga_pc200
aha1542
airlbios
aleck64
alg_bios
allied
alto2_cpu
amiga_ar1
amiga_ar2
amiga_ar3
ap2000
aristmk5
aristmk6
ar_bios
atarisy1
at_keybc
awbios
bbc_acorn1770
bbc_acorn8271
bbc_cumana1
bbc_cumana2
bbc_opus1770
bbc_opus2791
bbc_opus2793
bbc_opus3
bbc_weddb2
bbc_weddb3
betadisk
bml3kanji
bml3mp1802
bml3mp1805
bsmt2000
bubsys
buddha
bw2_ramcard
c1526
c1540
c1541
c1541c
c1541dd
c1541ii
c1541pd
c1541pdc
c1551
c1563
c1570
c1571
c1581
c2031
c2040
c2040fdc
c3040
c4023
c4040
c64_cs
c64_fcc
c64_mscr
c64_nl10
c64_supercpu
c64_xl80
c8050
c8050fdc
c8250
c8250lp
c8280
cbm2_hrga
cbm2_hrgb
cbm8000_hsg_a
cbm8000_hsg_b
cdibios
cedmag
cffa1
cga
cga_iskr1030m
cga_iskr1031
cga_m24
cga_mc1502
cga_poisk2
cgenie_fdc
chihiro
clgd542x
cmdhd
coco3_hdb1
coco_fdc
coco_fdc_v11
coco_t4426
coh1000a
coh1000c
coh1000t
coh1000w
coh1001l
coh1002e
coh1002m
coh1002v
coh3002c
coh3002t
compiskb
comx_clm
comx_eb
comx_epr
comx_fd
comx_pl80
comx_prn
comx_thm
cp400_fdc
cpc_brunword4
cpc_ddi1
cpc_dkspeech
cpc_hd20
cpc_mf2
cpc_ser
cpc_serams
cpc_smartwatch
cpc_ssa1
cpc_transtape
crvfdc01
crvfdc02
crysbios
csd1
cubo
cuda
d2fdc
d9060
d9090
decocass
dectalk_isa
dj2db
djdma
dms3d2kp
dmv_k220
dmv_k230
dmv_k231
dmv_k235
dmv_k806
dmv_keyb
dm_clgd5430
dragon_fdc
dsp1bleg
dsp1leg
dsp1leg_hi
dsp2leg
dsp3leg
dsp4leg
dw_kbd
e01
e01s
ec1840_0002
ec1841_0002
ef9365
ega
egret
electron_m2105
electron_plus3
ep64_exdos
epson_pf10
epson_tf20
et4000
ex800
f355bios
f355dlx
fccpu20
fccpu21
fccpu21a
fccpu21b
fccpu21s
fccpu21ya
fccpu21yb
fcisio1
fcscsi1
fc_disksys
fd2000
fd4000
fdc344
fdcmag
filetto_cga
finalchs
fsd1
fsd2
galgbios
gfxultra
gfxultrp
gic
gp_110
gq863
grip
gts1
gts1s
hardbox
hd44780_a00
hd61830
hdc
hdc_ec1841
hikaru
hng64
hod2bios
hp98034
hp98035
ibm_mfc
ibm_vga
ie15_keyboard
imi5000h
indusgt
interpod
intv_ecs
intv_voice
iq151_disc2
iq151_minigraf
iq151_ms151a
iq151_video32
iq151_video64
isa_hercules
isa_ibm_mda
isa_ibm_pgc
isbc_215g
isgsm
iteagle
jasmin
jvs13551
k573dio
k573mcr
k573msu
k573npu
k7659kb
kb_3270pc
kb_ec1841
kb_iskr1030
kb_pcat84
kb_pcxt83
kc_d004
kc_d004gide
keytronic_pc3270
km035
konamigv
konamigx
ks0066_f05
kviper
laserfdc
ldv1000
lindbios
lk201
lux10828
lux21046
lux21056
lx800
lx810l
m1comm
m20_8086
m24_kbd
m24_z8000
m50458
m68705p3
m68705p5
m68705r3
m68705u3
mach64
mackbd
macsbios
maxaflex
mc1502_rom
megaplay
megatech
microdisc
midcsd
midssio
mie
minichif
mm1kb
mpu401
ms7004
mshark
msm6222b
msx_cart_bm_012
msx_cart_sfg01
msx_cart_sfg05
msx_moonsound
ms_natural
mvme350
namco50
namco51
namco52
namco53
namco54
namco62
namcoc69
namcoc70
namcoc74
namcoc75
namcoc76
naomi
naomi2
naomigd
nb_48gc
nb_824gc
nb_aenet
nb_amc3b
nb_cb264
nb_image
nb_m2hr
nb_m2vc
nb_rtpd
nb_sp8s3
nb_spdq
nb_vikbw
nb_wspt
neogeo
newbrain_eim
newbrain_fdc
nmk004
nsmdsa
nsmdsad
nss
o2_voice
p1_fdc
p1_hdc
p1_rom
p72
pc1512kb
pc1640_iga
pcd_kbd
pcd_video
pcx_video
pd3_30hr
pd3_c264
pd3_lviw
pd3_mclr
pd3_pc16
pdc
pds_sefp
pet_softbox
pet_superpet
pgm
playch10
pr8210
psx_cd
pyson
ql_cumanafdi
ql_gold
ql_kdi
ql_mhd
ql_mpfdi
ql_opdbm
ql_pcmlqdi
ql_qdisc
ql_qplus4
ql_qubide
ql_sdisk
ql_sqboard256
ql_sqboard512
ql_sqmouse
ql_sqmouse512
ql_trump
ql_trump256
ql_trump512
ql_trump768
qsound
s1410
s3virge
s3virgedx
s3_764
saa5050
saa5052
sammymdl
sb16
sdtandy_fdc
sed1200
segadimm
segasp
serbox
seta10leg
seta11leg
sfcbox
sfd1001
shtzone
side116
simutrek
skns
slutprov
sns_rom_sgb
sns_rom_sgb2
spc1000_fdd_exp
stereo_fx
stic
stvbios
su2000
sv603
sx1541
sys246
sys256
sys573
t5182
taitotz
tetriskr_cga
tgui9680
ti99_bwg
ti99_evpc
ti99_fdc
ti99_gkracker
ti99_hfdc
ti99_myarcmem
ti99_pcode
ti99_rs232
ti99_speech
tiki100_8088
tms32031
tms32032
tourvis
triforce
tvc_hbf
uni800
unidisk
upd7220
v4bios
vic1515
vic1520
vic20_fe3
victor9kb
victor9k_fdc
videopak
votrax
vp700
vz_rs232
vz_rtty
wangpckb
wangpc_lic
wangpc_rtc
wangpc_wdc
wd1002a_wx1
wdxt_gen
wordpro
wyse700
x68k_cz6bs1
x820kb
xtide
ym2608
zorba_kbd
« Last Edit: February 08, 2017, 05:12:36 am by haynor666 »