[InactiveUser45]

In other news, the emulated Indy now has networking if you build from the latest GitHub sources. I haven't been able to figure how to properly set up the virtual adapter on Linux that MAME wants so I can't actually test whether it has internet access.

That's great news !

Although I don't know how to set up the required bits on Linux to make MAME networking work, I have found a few places that describe how to do it on Microsoft Windows. It basically boils down to installing OpenVPN and TAP, creating TAP devices with a .bat file, and then telling MAME in the machine specific .cfg file to use it. And creating a 'bridge' between the TAP devices and your real network interface.

PS: I tried to supply the links to the relevant forums posts, but somehow it seems that this forum doesn't like it when I post links. (presumably in order to prevent spammers from linking to malware hosting websites ?)

---

PS2: I assume the same general procedure of 'create TAP devices, bridge them to your real network interface, tell MAME to use the TAP device' applies to Linux as well.

Since QEMU also can make use of TAP devices, perhaps pointers on how to do it for MAME can be found in articles/posts on how to setup the TAP/bridge on Linux for QEMU? Just a thought.

[Raion]

QEMU doesn't work for IRIX or SGI equipment.

As for the issues posting links, you're a brand new account and the forum's anti-spam system called Cleantalk prefers for a user to have some participation before doing so.

Also avoid domains known for hosting spam or malware/warez, and don't use link shorteners.

[InactiveUser45]

QEMU doesn't work for IRIX or SGI equipment.

I get that, but that's not what I meant to say. What I am trying to say is that QEMU, like MAME, can make use of TAP devices to enable networking, and that probably means that the 'setup TAP' part is the same for both MAME and QEMU on Linux (it is on MS-Windows). (How you tell the emulator to use the TAP device is obviously different).

---

As for the issues posting links, you're a brand new account and the forum's anti-spam system called Cleantalk prefers for a user to have some participation before doing so.

Yeah, I suspected something like that. Thanks for clarifying that.

Also avoid domains known for hosting spam or malware/warez, and don't use link shorteners.

The links I was trying to post are to 'forum.arcadecontrols.com' and 'forum.mamedev.org', which are legitimate sites as far as I know.

[Raion]

That's fine, it's probably just your account age. If you have further issues, notify me and I'll help you out

[InactiveUser45]

OK, so here are the links that both describe how to setup MAME networking on MS-Windows. Perhaps someone else knows ho to do it on Linux.

[1]
http://forum.arcadecontrols.com/index.ph...msg1703641

[2]
https://forum.mamedev.org/viewtopic.php?...1481#p1481

[tallen]

I have a need (desire) to restore some older storage tapes from a Sony DDS-3 external drive (SDT-9000) that I used back in my irix days. Any chance I could use the emulator to perhaps 'tar' or 'bru' the dds tapes? I know it's a long shot.


History: I do have a scsii card that is recognized by a windows NT platform (has to be a 32-bit OS), but aside from getting the external tape drive to mount (without issue), I've had zero luck in getting the tape heads to move. I've taken great care of the device, so I'm fairly confident it will work. The device turns on and off quite nicely, no errors. I guess my big question is whether evaluator irix will recognize the device that's mounted to my pc, and for that matter whether I can perform a tar or bru. I do not recall using an interface when backing up and restoring to/from my irix systems, gosh it was a long time ago... but I do recall me tar'ing off the data from my drives to the dds unit.


What do you think? Reaching out here for some thoughts/opinions, thx.

[Raion]

Currently no, emulation will not support something like this from my understanding. The ability to attach SCSI devices is moreorless limited to hard disks, and it's unlikely that MAME has any code to handle this case.

You're welcomed to try. But I would first make a new thread and maybe someone with an IRIX machine near you can dump the tapes for you and then you can return to this for science.

Not to mention, if you use an old enough machine with 32-bit windows, I don't think that you're going to get sufficient performance to make it worth your while. It could take days or hours to dump the tapes if the system has less than a fifth of the speed of a real device. That'll certainly cause damage to a very old tape drive because it probably isn't going to be able to run continuously.

[jan-jaap]

There's no need for emulation. Just use whatever Linux PC with a compatible SCSI interface to read the tapes. Or a SUN workstation. You might be able to get away with a Windows PC with cygwin (just don't ask me for help with that one).

You will need to know how the tapes were created (tar? cpio? bru?) and maybe some parameters like block size, but the same is true for restoring with IRIX. When in doubt just dump the tape to disk with 'dd' and see what 'file' thinks it is. You may need to do some post processing like byte swapping but that's the least of your worries..

[InactiveUser45]

In other news, the emulated Indy now has networking if you build from the latest GitHub sources. I haven't been able to figure how to properly set up the virtual adapter on Linux that MAME wants so I can't actually test whether it has internet access.

Hi,

By the way, do you know how to tell the emulated indy_4610 that it has an ethernet card ? When I run 'mame64 -listslots indy_4610' for MAME 0.220, get a lot of results - but no ethernet card : (or do we have to wait for MAME 0.221 ?)

[shrek]

The network adapter is there by default as of 0.220 but not listed in the machine options. Just start the Indy as you normally would. When you boot into IRIX and go to the settings program it will detect the Ethernet interface just fine and configure it successfully. The point I got stuck at was creating the virtual TUN/TAP adapter that MAME wants to use to give it internet access.