Identifying PCB revision

big10p · Jan 21, 2026

I'm thinking of doing a HSS patch mod to my Time Pilot '84 and need to identify which revision I have, to apply the correct patch.

The screen printed text just above the edge connector has (B) in it, so I'm guessing it's revision B?

The board only has mask ROMs so wasn't sure what to set my EPROM programmer to in order to dump one for romident. Looks like they're 8k ROMs? Can I read them by simply specifying a generic 2764?

Thanks.

big10p · Jan 21, 2026

The image got compressed, so here's a couple showing ROMs more clearly

big10p · Jan 21, 2026

Oh wait, maybe 16k ROMs.

NivagSwerdna · Jan 21, 2026

GX388 is Time Pilot 84

ROMs are 2764

big10p · Jan 21, 2026

NivagSwerdna said:
GX388 is Time Pilot 84

ROMs are 2764

Not 27128? The ROMs have 128 on them. Can confirm revision B board? Thanks.

NivagSwerdna · Jan 21, 2026

Ah I see

Looking at the Time Pilot 84 schematic I can see that either 2764 are populated or half the number of 27128 and the jumper JP3/JP4 is moved.

I guess you have the 27128 flavour; differs at pin 26.

As for Rev B... No ideal what that refers to.. GX388 is Time Pilot 84 and the later GX393 would be Time Pilot.

Read them as 27128 and see what happens; harmless to a 2764.

big10p · Jan 21, 2026

NivagSwerdna said:
Ah I see

Looking at the Time Pilot 84 schematic I can see that either 2764 are populated or half the number of 27128 and the jumper JP3/JP4 is moved.

I guess you have the 27128 flavour; differs at pin 26.

As for Rev B... No ideal what that refers to.. GX388 is Time Pilot 84 and the later GX393 would be Time Pilot.

Read them as 27128 and see what happens; harmless to a 2764.

Ok, I'll try reading one as a 27128. Just didn't want to accidentally damage one.

Arcade ROM Patcher has patches for 4 different versions. Just trying to identify which one applies to my board.

big10p · Jan 21, 2026

Can't seem to read them as 27128 ROMs. Get a pin error for pin 1.

stevebm1 · Jan 21, 2026

which eprom programmer are you using?,have you unchecked the box for check id in the software?,sometimes that helps

big10p · Jan 21, 2026

stevebm1 said:
which eprom programmer are you using?,have you unchecked the box for check id in the software?,sometimes that helps

It's a T48. I unchecked the ID check box. That's caught me out before. Maybe the T48 just can't read these. 🤷‍♂️

NivagSwerdna · Jan 21, 2026

Well I'm a bit disappointed by that...

and

I thought that looked like a sure thing.

and would hope to end up with...


ROM_START( tp84b )
    ROM_REGION( 0x10000, "cpu1", ROMREGION_ERASE00 )
    // 0x6000 - 0x7fff space for diagnostic ROM
    ROM_LOAD( "388j05.8j",   0x8000, 0x4000, CRC(a59e2fda) SHA1(7d776d5d3fcfbe81d42580cfe93614dc4618a440) )
    ROM_LOAD( "388j07.10j",  0xc000, 0x4000, CRC(d25d18e6) SHA1(043f515cc66f6af004be81d6a6b5a92b553107ff) )

    ROM_REGION( 0x10000, "sub", 0 )
    ROM_LOAD( "388j08.10d", 0xe000, 0x2000, CRC(2aea6b42) SHA1(58c3b4852f22a766f440b98904b73c00a31eae01) )

    ROM_REGION( 0x4000, "audiocpu", ROMREGION_ERASE00 )
    ROM_LOAD( "388j13.6a", 0x0000, 0x2000, CRC(c44414da) SHA1(981289f5bdf7dc1348f4ca547ac933ef503b6588) )

    ROM_REGION( 0x4000, "tiles", 0 )
    ROM_LOAD( "388j02.2j",  0x0000, 0x4000, CRC(e1225f53) SHA1(59d07dc4faafc82999e9716f0bba1cb7350c03e3) )

    ROM_REGION( 0x8000, "sprites", 0 )
    ROM_LOAD( "388j09.12a", 0x0000, 0x4000, CRC(aec90936) SHA1(3420c24bbedb140cb20fdaf51acbe9493830b64a) )
    ROM_LOAD( "388j11.14a", 0x4000, 0x4000, CRC(29257f03) SHA1(ebbb980bd226e8ada7e517e92487a32bfbc82f91) )

    ROM_REGION( 0x0500, "proms", 0 )
    ROM_LOAD( "388j14.2c",  0x0000, 0x0100, CRC(d737eaba) SHA1(e39026f87f5b995cf4a38b5d3d3fee7561762ae6) ) // palette red component
    ROM_LOAD( "388j15.2d",  0x0100, 0x0100, CRC(2f6a9a2a) SHA1(f09d8b92c7f9bf046cdd815c5282d0510e61b6e0) ) // palette green component
    ROM_LOAD( "388j16.1e",  0x0200, 0x0100, CRC(2e21329b) SHA1(9ba8af294dbd6f3a5d039c74a56e0605a913c037) ) // palette blue component
    ROM_LOAD( "388j18.1f",  0x0300, 0x0100, CRC(61d2d398) SHA1(3f74ad733b07b6a31cf9d4956d171eb9253dd6bf) ) // char lookup table
    ROM_LOAD( "388j17.16c", 0x0400, 0x0100, CRC(13c4e198) SHA1(42ab23206be99e840bd9c52cefa175c12fac8e5b) ) // sprite lookup table
ROM_END

i.e.

ROM_LOAD( "388j09.12a", 0x0000, 0x4000, CRC(aec90936) SHA1(3420c24bbedb140cb20fdaf51acbe9493830b64a) )
ROM_LOAD( "388j11.14a", 0x4000, 0x4000, CRC(29257f03) SHA1(ebbb980bd226e8ada7e517e92487a32bfbc82f91) )

NivagSwerdna · Jan 21, 2026

^ If you compare your photo with the MAME entries...

388j09 & 388j11

big10p · Jan 21, 2026

NivagSwerdna said:
Well I'm a bit disappointed by that...

View attachment 51842
and

View attachment 51843

I thought that looked like a sure thing.

and would hope to end up with...

ROM_START( tp84b ) ROM_REGION( 0x10000, "cpu1", ROMREGION_ERASE00 ) // 0x6000 - 0x7fff space for diagnostic ROM ROM_LOAD( "388j05.8j", 0x8000, 0x4000, CRC(a59e2fda) SHA1(7d776d5d3fcfbe81d42580cfe93614dc4618a440) ) ROM_LOAD( "388j07.10j", 0xc000, 0x4000, CRC(d25d18e6) SHA1(043f515cc66f6af004be81d6a6b5a92b553107ff) ) ROM_REGION( 0x10000, "sub", 0 ) ROM_LOAD( "388j08.10d", 0xe000, 0x2000, CRC(2aea6b42) SHA1(58c3b4852f22a766f440b98904b73c00a31eae01) ) ROM_REGION( 0x4000, "audiocpu", ROMREGION_ERASE00 ) ROM_LOAD( "388j13.6a", 0x0000, 0x2000, CRC(c44414da) SHA1(981289f5bdf7dc1348f4ca547ac933ef503b6588) ) ROM_REGION( 0x4000, "tiles", 0 ) ROM_LOAD( "388j02.2j", 0x0000, 0x4000, CRC(e1225f53) SHA1(59d07dc4faafc82999e9716f0bba1cb7350c03e3) ) ROM_REGION( 0x8000, "sprites", 0 ) ROM_LOAD( "388j09.12a", 0x0000, 0x4000, CRC(aec90936) SHA1(3420c24bbedb140cb20fdaf51acbe9493830b64a) ) ROM_LOAD( "388j11.14a", 0x4000, 0x4000, CRC(29257f03) SHA1(ebbb980bd226e8ada7e517e92487a32bfbc82f91) ) ROM_REGION( 0x0500, "proms", 0 ) ROM_LOAD( "388j14.2c", 0x0000, 0x0100, CRC(d737eaba) SHA1(e39026f87f5b995cf4a38b5d3d3fee7561762ae6) ) // palette red component ROM_LOAD( "388j15.2d", 0x0100, 0x0100, CRC(2f6a9a2a) SHA1(f09d8b92c7f9bf046cdd815c5282d0510e61b6e0) ) // palette green component ROM_LOAD( "388j16.1e", 0x0200, 0x0100, CRC(2e21329b) SHA1(9ba8af294dbd6f3a5d039c74a56e0605a913c037) ) // palette blue component ROM_LOAD( "388j18.1f", 0x0300, 0x0100, CRC(61d2d398) SHA1(3f74ad733b07b6a31cf9d4956d171eb9253dd6bf) ) // char lookup table ROM_LOAD( "388j17.16c", 0x0400, 0x0100, CRC(13c4e198) SHA1(42ab23206be99e840bd9c52cefa175c12fac8e5b) ) // sprite lookup table ROM_END

i.e.

ROM_LOAD( "388j09.12a", 0x0000, 0x4000, CRC(aec90936) SHA1(3420c24bbedb140cb20fdaf51acbe9493830b64a) )
ROM_LOAD( "388j11.14a", 0x4000, 0x4000, CRC(29257f03) SHA1(ebbb980bd226e8ada7e517e92487a32bfbc82f91) )

Problem solved! Turns out I needed to uncheck a Pin Detect box in my reader software, as well as the ID check.

Turns out mine is indeed revision B. Tp84b (set 3) in MAME.

Thanks!

Identifying PCB revision

big10p

Coins detected in pocket!

big10p

Coins detected in pocket!

big10p

Coins detected in pocket!

NivagSwerdna

Active member

big10p

Coins detected in pocket!

NivagSwerdna

Active member

big10p

Coins detected in pocket!

big10p

Coins detected in pocket!

stevebm1

Active member

big10p

Coins detected in pocket!

NivagSwerdna

Active member

NivagSwerdna

Active member

big10p

Coins detected in pocket!

Related Links

Related Links

Get In Touch