fun!
There is a huge variety of MAME frontends on the web, some excellent and some in developement :)
AdvanceMenu is my first choice of frontend
My PC does not have a useable keyboard, it doesn't boot into Windows and the PC components are mounted inside a JAMMA cabinet
The cabinets joystick buttons and coin mechenism are connected directly to the PC via a J-PAC keyboard encoder
For me the beauty of AdvanceMenu is that it allows you to reconfigure virtually everything to do with the frontend, including the keys to navigate through the system
This is vital for my setup as I do not have a keyboard!
Another DOS based frontend worth mentioning is ArcadeOS from the ArcadeOS team. This has slightly more features but currently seems to be struggling with the newest MAME beta's - its nice though :)
If you run Windows9x/ME in a normal PC, Emu Loader is a good choice for running DOS as it is nice to use and very configurable. Emu Loader also allows you to display both screen shots and flyers. You could also run the DOS frontends in a Windows DOS window too
MAME is capable of natively running on several monitor platforms. These are :
Standard PC monitor (default (S)VGA etc.)
PAL monitor (low res TV screen)
NTSC monitor (low res TV screen)
Arcade monitor (15.725Khz)
Arcade monitors are technically similar to an NTSC TV's without the tuner hardware, PAL TV's run at a slightly different frequency.
I CAN NOT EMPHASISE ENOUGH HOW MUCH OF A DIFFERENCE DISPLAYING MAME ON AN ARCADE/TV MONITOR MAKES. GAMES WHICH LOOK OLD, DATED AND BLOCKY, COME TO LIFE AS THE LOW RESOLUTION OF THESE DISPLAYS SIGNIFICANTLY REDUCE THE BLOCKYNESS AND THERE IS NO NEED TO MESS ABOUT SETTING UP MAME TO EMULATE THIS "LOW RES" EFFECT BY USING SCANLINES OR OTHER METHODS WHICH ULTIMATELY HAVE A PERFORMANCE HIT ON YOUR SYSTEM.
If you need to run MAME on an arcade or NTSC monitor you will need to make up a cable to connect to your monitor from the VGA card
You will also need a frontend capable of displaying NTSC frequencies as DOS can not output to this type of display without a TSR to convert the output frequency. ArcadeOS has this built in using the incabinet=1 option.
Alternatively, you can use a standard TV (PAL or NTSC) to run MAME using a video card with TV-OUT capabilities. This has the added bonus of being able to display Windows.
Want to run Windows in 640x480 using an ordinary VGA card on a 15 kHz arcade monitor by only using software?
Using a supported card, you can set the VESA BIOS to match 15 kHz frequency needed by the monitor
To do this you must use AdvanceVBE made by Andrea Mazzoleni @ http://advancemame.arcadeheaven.com
Download AdvanceCAB from AdvancedMAME's site
Run MV.EXE to test all of the video modes with your card/monitor, plus a 640x480 16 bit-mode for Windows
Run the TSR VBE.COM which allows you to run the video modes on your 15KHz arcade monitor
Apparently Windows 98 runs great on it, with 65536 colors in an interlaced mode!
Even Andrea didn't know about it, actually he said Windows isn't supported because he never tried. I (Filipe Estima) did and he got surprised :o)
Thanks to Filipe Estima for donating this information :)
I haven't tried this configuration
If you do not have access to an arcade monitor you can cheeply buy 21" screen TV's with SCART inputs. Standard TV's are virtually the same as arcade monitors, with the addition of a TV tuner.
My arcade cabinet runs AdvanceMame via a Matrox G400 and a VGA to SCART to a UK spec PAL TV
Obviously to display a picture there has to be a trade off between functionality and 'arcade' quality
Normal VGA cards run at a frequency too high to display a picture on a PAL/NTSC Tv or arcade monitor via the VGA port
To achieve the correct frequencies so I can see DOS, I use a small driver called VGA-TV
This converts the scrambled VGA pictures to PAL/NTSC/Arcade (see pictures at the bottom of the page)
On the down-side to this configuration, I am unable to view the BIOS or anything BEFORE VGA-TV loads - I use a TV-OUT card to modify the BIOS....which is never really!
I DO NOT RECOMMEND ANYONE SHOULD ATTEMPT THIS. TV & ARCADE SCREENS CAN KILL IF NOT HANDLED CORRECTLY EVEN WHEN NOT PLUGGED INTO THE ELECTRICITY SUPPLY
I CAN NOT EMPHASIZE ENOUGH HOW MUCH OF A DIFFERENCE DISPLAYING MAME ON AN ARCADE/TV MONITOR MAKES. GAMES WHICH LOOK OLD, DATED AND BLOCKY, COME TO LIFE AS THE LOW RESOLUTION OF THESE DISPLAYS SIGNIFICANTLY REDUCE THE BLOCKYNESS AND THERE IS NO NEED TO MESS ABOUT SETTING UP MAME TO EMULATE THIS "LOW RES" EFFECT BY USING SCANLINES OR OTHER METHODS WHICH ULTIMATLEY HAVE A PERFORMANCE HIT ON YOUR SYSTEM
The video card is connected to the TV using the composite video out socket of my video card directly into the TV's SCART socket which accepts composite video in
21 Ground/Shield 19 Composite Video Out 17 Composite Video Ground 15 red / Chroma 13 Red Ground 11 Green 9 Green ground 7 Blue 5 Blue ground 3 Audio out L & mono 1 Audio out R |
 |
20 Composite Video In / Luminance 18 Blanking Signal Ground 16 Blanking Signal 14 Data Ground 12 Data out 10 Clock out 8 Audio / RGB Switch16:9 6 Audio In Left & Mono 4 Audio Ground 2 Audio In Right |
|
||
1 Red Video 2 Green Video 3 Blue Video 4 ID Bit 2 5 GND N/A Ground 6 RGND N/A Red Ground 7 GGND N/A Green Ground 8 BGND N/A Blue Ground |
|
9 KEY N/A Key (No pin) 10 SGND N/A Sync Ground 11 ID Bit 0 12 ID Bit 1 13 HSYNC or Composite Sync 14 VSYNC Vertical Sync 15 ID Bit 3 |
To connect a VGA card to a SCART socket, simply buy a cheap VGA extension cable and chop off the end that does NOT connect to the VGA card - the chopped end will become the SCART side.
Measure out with a multi-meter, the bare wires from the VGA side (table below, left) and solder onto the SCART side (table below, right)
15 PIN VGA |
CONNECT TO |
21 PIN SCART / PERITEL |
1 Red Video |
- |
15 Red |
2 Green Video |
- |
11 Green |
3 Blue Video |
- |
7 Blue |
13 Horizontal Sync |
- |
20 Composite Video In |
15 Vertical Sync |
- |
20 Composite Video In |
ALL Grounds |
- |
21 Ground |
If you experience problems with sync-ing AFTER you run the TV-VGA driver, try connecting pin 20 (Composite Sync) to Pin 16 (Blanking Signal)
The principals for connecting mame to an arcade monitor are similar to the SCART config, the only difference will be the connectors to your monitor, which are unique to the monitor
Before You Begin
You must understand your network.
Download the MS-DOS NETWORK CLIENT DISK 1 & 2 from the DOWNLOAD section
A computer with MS-DOS installed on it.
Your network card is NDIS 2.0 compliant and you have the DOS network drivers for it
Note The Microsoft Network Client for MS-DOS works with any version of MS-DOS between 3.2 and 6.22 inclusive; however, you may need to refer to the manufacturer of the network interface card (NIC) for the version of MS-DOS the NIC requires.
After the files are copied onto both disks, the installation disk set is ready for use.
Running Setup on the Workstation
At the Setup screen, press ENTER to continue with Setup. You will be prompted to provide a directory that will contain the networking files, and it is recommended that you use the default directory (C:\Net).
Provide the directory, and then press ENTER to continue.You will be prompted to select a network interface card (adapter). Select your adapter from the list, and then press ENTER.
If you do not find your network interface card in the list, choose Network adapter not shown on list below, and then press ENTER.
You will be prompted for the location of the network interface driver files.
These files are provided by the manufacturer of the network interface card.
The driver must be NDIS 2.0-compliant, and will be accompanied by an Oemsetup.inf file that is also provided by the manufacturer.
Press ENTER, and continue.You will be prompted for your user name.Type your user name, and then press ENTER.This will take you to the Setup menu.
The Setup Menu
The Setup menu gives you three options:
Change names: Allows you to change the user name, computer name, workgroup name, and the domain name.
Change Setup Options: Allows you to change the redirector option, startup options, logon type, and set hot keys.
Change network Configuration: Allows you to add and remove network adapters and protocols. It also allows you to change settings related to the protocol or network adapter.
Use the UP ARROW and DOWN ARROW keys to select an option, and then press ENTER. You will be given a new menu associated with your choice from above.
If all of the options have been set, select The listed options are correct, press ENTER, and the Setup program will complete the installation process. Depending on your selections, you might not use Disk #2 of the installation set.
The Change Name Menu
If you select Change names in the Setup menu, you will see the following menu.
The options for this menu are:
Change User name
Change Computer Name
Change Workgroup Name
Change Domain Name
The listed options are correct
Use the UP ARROW and DOWN ARROW keys to select an option, and then press ENTER. Type the new information in the field that follows, and then press ENTER. If all of the options have been set, select The listed options are correct, and press then ENTER to return to the Setup menu for new options, or to complete the installation process.
The Change Setup Options Menu
If you select Change Setup Options in the Setup menu, you will see the following menu.
The options for this menu are:
Change Redir Options: Choose either the full or basic redirector. The full redirector is used for logging on to a Microsoft Windows NT or LAN Manager domain, or if you run programs that use advanced network functions such as named pipes. The basic redirector provides all standard workgroup functions such as connecting and disconnecting. It uses less memory and disk space than the full redirector. You must use the basic redirector if your computer has an 8088 processor.
Change Startup Options: Allows you to configure the computer to automatically start the Microsoft Network Client for MS-DOS or both the Network Client and Pop-up Interface.
Change logon Validation: Allows you to choose whether to log on to a domain.
Change Net Pop hot Key: Allows you to select a particular key to used in conjunction with CTRL+ALT, to activate the pop-up interface.
Use the UP ARROW and DOWN ARROW keys to select an option, and then press ENTER. Change the options as necessary, and then press ENTER. If all of the options have been set, select The listed options are correct, and then press ENTER to return to the Setup menu for new options, or to complete the installation process.
The Change Network Configuration Menu
If you select Change Network Configuration in the Startup menu, you will see the following menu.
This menu is different than the others because it has a double window. The selections that are ed in the upper and lower windows are directly related. The active window is indicated by a double white outline. You use the TAB key to activate the upper or lower window. After the window is active, you can use the UP ARROW and DOWN ARROW keys to select an option.
The upper window shows the installed adapters and protocols. The lower window has the following options:
Change Settings: This option allows for settings to be made to the adapter or protocol that is currently ed in the upper window. If you are changing settings and a network adapter is selected, you may have the option to change some of the settings, such as driver name, IRQ, I/O address, and more. It is usually best to use the manufacturer's suggested settings if possible.
If you are changing settings to the NetBEUI protocol, you can change the Maximum Sessions or the NCBS setting.
If you are changing settings to the NWLink protocol, you can change the frame type from the default 802.2 (Ethernet_802.2) to any of the following: Ethernet_802.3, Ethernet_II, Ethernet_SNAP, or TOKENRING.
If you are changing settings to the TCP/IP protocol, you can enable or disable the Domain Host Configuration Protocol (DHCP), input the IP address, subnet mask, and up to two default gateways, and set the number of NetBIOS sessions.
Note The format of all IP addresses in this section is based on spaces replacing the dots that separate the octets (that is, 127 0 0 1 instead of 127.0.0.1).
Remove: Remove whatever network adapter or protocol is currently ed in the upper window.
Add Adapter: Allows you to add a network adapter, and adds it to the upper window.
Add Protocol: Allows you to add another protocol, and adds it to the upper window.
Use the UP ARROW and DOWN ARROW keys to select an option, and then press ENTER. Change the options as necessary. If all of the options have been set, select The listed options are correct, and then press ENTER to return to the Setup menu for new options, or to complete the installation process. Modifying the Startup Disk for NWLink Frame Types.
Finish the Microsoft Network Client for MS-DOS installation on the computer or the installation of files on the startup disk.
In the network installation directory ("Net" directory on the startup disk or on the computer's hard disk drive, unless the directory name was changed during installation), open the Protocol.ini file in Notepad or a text editor. Look for the protocol section of the file; it is preceded by a header, which appears as follows:
[ms$nwlink]
Under the title, find the value that appears as follows:
FRAME=Ethernet_802.2
This is the default setting. Change "Ethernet_802.2" to the appropriate frame type for your network. The frame types available must be input exactly as they appear here. The choices are as follows:
Ethernet_802.2
Ethernet_802.3
Ethernet_II
Ethernet_SNAP
TOKENRING
Save the changes in the Protocol.ini file. Modifying the Startup Disk for Network Interface Cards Not in the List.
Modifying the Startup Disk for network interface cards (NIC) not in the list requires installing the appropriate MS-DOS driver and editing two system files.
Install an NDIS2-compatible MS-DOS driver for the NIC. These are usually included with the floppy disk supplied by the manufacturer with their drivers. If no drivers are available, download the appropriate driver from the manufacturer's Web site.
Appropriate drivers for the Microsoft Network Client for MS-DOS will always have a .dos extension. For example, the driver for Intel's EtherExpress Pro/10 EISA is:
Epro.dos
This driver should be placed in the Net directory on the computer (C:\Net, unless named differently) or on the MS-DOS startup disk (A:\Net).
Modify the System.ini file. The NIC driver needs to be referenced in the System.ini file. This entry is found in the [network drivers] section, as illustrated below:
[network drivers]
netcard=elnkii.dos
transport=ndishlp.sys,*netbeui
devdir=A:\NET
LoadRMDrivers=yes
For "netcard=," replace the current driver with the file name of the NDIS2-compatible driver placed in the Net directory (for example, Epro.dos).
Modify the Protocol.ini file. The NIC driver needs to be referenced in the Protocol.ini file. This entry is found in the [ms$ driver_name] section (the driver name will reflect what was originally chosen in the Network Installation Startup Disk process), as shown below:
[ms$elnkii]
drivername=ELNKII$
; INTERRUPT=3
; IOADDRESS=0x300
; DMACHANNEL=1
; MAXTRANSMITS=12
For "drivername=," replace the driver listed with the file name of the NDIS2-compatible driver; use a dollar sign ($) to replace the .dos file extension (for example, EPRO$).
Note Do not change the header (for example, [ms$elnkii] in the example above); the header is a pointer throughout the .ini file. Additional TCP/IP Settings for the Microsoft Network Client for MS-DOS.
Specifying WINS Servers
If your Microsoft Network Client for MS-DOS uses DHCP (the default setting for MS-DOS TCP/IP), it will automatically receive the address for the Windows Internet Naming Service (WINS) server. If you want to statically configure your WINS server IP address, you must edit the client's Protocol.ini file and add the IP address to the [TCPIP] section.
For example, if you have two WINS servers available, add them into the [TCPIP] section as shown in the example below. Note that there are no dots (.) in the IP addresses.
[TCPIP]
WINS_SERVER0 = 11 101 13 53
WINS_SERVER1 = 11 101 12 198
Name queries will be sent to the WINS servers in the order in which they appear in the .ini file. The ipconfig command may show a different order of WINS servers (or even different WINS servers altogether) —these are the WINS server names sent by DHCP, and the Protocol.ini settings override them.
Important There is a difference in functionality available in TCP/IP for Microsoft® Windows® for Workgroups, Windows NT Workstation, and Windows NT Server, versus MS-DOS TCP/IP. Specifically, an MS-DOS TCP/IP client does not:
Support DNS resolution using WINS.
Support WINS resolution using DNS.
Register its name with the WINS database; it does queries only.
Logging On with TCP/IP Across a Router
If the domain controller is across a router from the Microsoft Network Client for MS-DOS computer, you must add a line to the client's LMHOSTS file (located in the Net directory — if there is no LMHOSTS file, you need to create one) for logons to be validated. The line has the following format:
www.xxx.yyy.zzz SRV_NAME #DOM:DOM_NAME
where:
www.xxx.yyy.zzz is the IP address of the domain controller.
SRV_NAME is the NetBIOS name of the domain controller.
DOM_NAME is the name of the domain.
You must also ensure that the domain controller can contact the Microsoft Network Client for MS-DOS using one of the following methods:
Enter the client's IP address and name in the domain controller's LMHOSTS file.
Register the client with a WINS server that is accessible by the domain controller (placing a static entry in WINS for the Microsoft Network Client for MS-DOS).
Ipconfig.exe and Controlling DHCP Leases
The Ipconfig.exe utility provides DHCP configuration information only. The version of Ipconfig.exe provided with the Microsoft Network Client for MS-DOS does not support command-line switches for controlling DHCP address leases; you must use the DHCP Administration Utility instead. References.
The following articles in the Microsoft Knowledge Base provide additional information on this topic.
Q135465 - README.TXT: Microsoft Network Client version 3.0
Q128800 - How to Provide Additional NDIS2 Drivers for Network Client 3.0[winnt]
Q142857 - How to Create a Network Installation Boot Disk
Q130875 - Troubleshooting MS Network Client 3.0 and DHCP
Q128751 - No "Advanced" button in Client TCP/IP Configuration Box
Q123285 - IPCONFIG Displays Invalid Results
Q130538 - DHCP-Enabled MS-DOS Clients Do Not Resolve Host Names
Once you have successfully installed your MS-DOS network client, you will notice you can only connect to remote computer shares on your network from your DOS PC - you can not share out your PC like in Windows.
To share your MS-DOS PC with other computers on your network you will have to replace your NET.EXE, NET.MSG and NETH.MSG files with server enabled versions.
THIS WILL NOT WORK FOR VERSIONS OF MS-DOS 7 OR HIGHER.
This is because SHARE.EXE is required by the server software. SHARE.EXE has been removed after MS-DOS 6.22 as it does not work with FAT32 in REAL DOS.
The server enabled versions can be found in the DOWNLOAD section.
Download the DOS CLIENT SERVER PATCH from the DOWNLOADS section.
Extract the files to C:\NET or into your MS-DOS network client path, overwriting NET.EXE, NET.MSG and NETH.MSG.
Edit your Autoexec.bat to include :
NET START SERVER
To start the server
Reboot your PC and you will notice if you type NET /? at the command prompt you will have a SHARE option
To see the SHARE options, type NET SHARE /? | MORE
To share a drive or folder with read/write access, simply use the syntax
NET SHARE [SHARE NAME]=[LOCAL PATH] /FULL:
eg.
NET SHARE MAME=C:\MAME /FULL:
The MS-DOS client will automatically remember your shares next time you reboot
Here are some connectivity examples for hub-to-hub, hub-to-transceiver, transceiver-to-transceiver, pinouts and color coding for standard ethernet cabling.
|
 |
|
||||||||||||||||||||||||
Please Note: The standard connector view shown is color-coded for a straight thru cable assembly, when connecting Hub to Xcvr or DNI Card. When connecting hub to hub, Xcvr to Xcvr, or DNI to DNI, the wires must crossover at the opposite end of the cable assembly.
Interconnecting Your Hubs, Transceivers, and DNI Cards
As noted in the illustrations below, a crossover cable is required when connecting a Hub to a Hub, or a Transceiver to Transceiver, or DNI to DNI card, or Transceiver to DNI card. When connecting a Hub to a transceiver or DNI card, a straight through cable is always used. Please Note: Some Cabletron products are equipped with internal switches that can internally cross the twisted pairs.
In these illustrations a Hub can refer to any standalone product, such as the SEHI or MicroMMAC; or concentrator modules in MMAC-FNB or MMACPLUS hubs, such as a TPMIM-xx, TPRMIM-xx or 9E132-15. To note the differences between Ethernet, Token Ring and FDDI/ATM connectivity. Hub to Hub Connectivity
Category 5 wiring standards: EIA/TIA 568A/568B and AT&T 258A define the wiring standards and allow for two different wiring color codes.
| Pin # | EIA/TIA 568A | AT&T 258A, or EIA/TIA 568B | Ethernet 10BASE-T | Token Ring | FDDI, ATM, and TP-PMD |
| 1 | White/Green | White/Orange | X | X | |
| 2 | Green/White | Orange/White | X | X | |
| 3 | White/Orange | White/Green | X | X | |
| 4 | Blue/White | Blue/White | X | ||
| 5 | White/Blue | White/Blue | X | ||
| 6 | Orange/White | Green/White | X | X | |
| 7 | White/Brown | White/Brown | X | ||
| 8 | Brown/White | Brown/White | X |
