Yes, I understand, but that was the initial scan of the new SPLIT 212 pack

Given there are two undumped internal roms in that chip (1M of wavetable, 256k of program) it's not going to happen any time soon :-)

It's incredible how this soviet character looks like Capt. Olimar of future Nintendo games. Maybe it's a secret inspiration of the Pikmin team.

meanwhile...


-Thom

It appears that ESC E/e pair just turn on/off double spacing. For every CR, you get an extra CR. BOGO.

I guess I was expecting it to be more complicated than that 8-)

It would've been cool if they'd included a sample basic program that would show how every ESC code worked. I think I'll write one.

One last mystery to solve is why the bidirectional printing doesn't line up properly. Sometimes it does, and other times it doesn't.

I noticed that if I printed a line that was over 40 characters long that it would be off by one pixel printing characters on the return trip leftward. When it prints less than 40 characters, it lines up perfectly.

There's a topic here which may be of help: https://www.arcade-projects.com/for...ut-from-sega-st-v-model-2-model-3-naomi/
And, more to the point: http://solid-orange.com/1431

forensic retrocomputing... sounds interesting

The hardware is annoyingly similar to the real thing, but not quite -- with these debugger hacks ACT passes and OS tries to boot from floppy, but halts halfway.



I suppose the next best thing is HLE, since hardware docs for actual storage controllers (iSBX clones) are missing.

It automatically saves the debugger window layout at the same time that it saves input mappings - it works the same way. The data isn't persistent while MAME is running, so if you start without the debugger, nothing handles it and it won't get saved out again.

SCC Localtalk is something we want to do, but it's a hard problem.

SCSI Ethernet isn't currently possible because of how we handle SCSI, and we need a cycle-interruptible 68k core to be able to fix that.

Well I got a bit further:

• Image loads are now reflected back onto profiles
• Save states are now persisted with profiles. Currently this is always on and there isn't a way to control it, but overall this proves out the idea.

So, BletchMAME profiles are now in a state with some semblance of usability. I suppose my next tasks are to kick the tires for a while.

Coming soon ...



Still plenty to do, especially keyboard.

Also have ROMs for the Husky Hawk and Hunter 2/16 but not enough known about them to make much progress, will probably submit as skeletons.

I always appreciate the help here and all the things the mame team has provided over the past 22 years. I finally just recompiled the latest version and deleted all my old cruft and setup the mame.ini properly and now it works as expected.

This is something on our radar (it'd be nice for the synthesizer drivers in order to have a local keyboard instead of sending them MIDI messages, plus the Keyboard Mania games) but I haven't quite come up with a design I like for it.

Yay! Christmas in July August! (With mame releases it's like Christmas every month!)

A compiling we will go...

Yes it is just a bit delayed.
Cuavas gave an official answer in MAME's Reddit yesterday: https://www.reddit.com/r/MAME/comme...so?utm_source=share&utm_medium=web2x

I've uploaded an archive with about 20 different EGA and VGA card BIOS, photos and some drivers and docs.

Install IRIX 6.5 onto an emulated Silicon Graphics INDY using MAME 0.211

This is basically an updated version of the previous post. Screenshots are not included because they are nearly identical to the previous post.


1) Get the software ready:

a) Be sure you have the correct Machine ROM in your roms folder; "indy_4610.zip".
There are some other ROMs we need for keyboard functionality.

kb_ms_natural.zip
ps2_keybc.zip

*Note: The "ps2_keybc.zip" files I found from my usual sources did not work. They were missing a file called "72x8455.zm82". I googled and found the file, then added it to my "ps2_keybc.zip".


b) Get the Install IRIX 6.5 install CD-ROM disc images from the Internet Archive (https://archive.org/) Search for "IRIX 6.5". I removed spaces and renamed the .img files as ".iso" to make the later commands simpler.

You need 4 disc images:
IRIX 6.5 Installation Tools June 1998
IRIX 6.5 Foundation 1
IRIX 6.5 Foundation 2
IRIX 6.5 Applications June 1998

c) Make a blank 12 GB Hard Drive using the chdman utility with this command:
chdman createhd -f -o irix12gbHD.chd -s $[12288*1572864]

I put all files (zip, iso and chd) in my "roms" folder to make the later commands simpler.


2) Boot the machine using the CD-ROM image, and mount the Hard Drive. The command I used also sets MAME into windowed mode (with the default resolution of an INDY system) to make it easier to move back and forth between the tutorial and MAME. I'm using a Mac laptop, so I use "fn" + "delete" key to partially escape the emulated keyboard. Then I can "command" + "tab" to switch between apps. Double check this function in the MAME docs for your system, so you do not get locked into the emulation keyboard with no way to escape.

Replace <PATH TO MAME FOLDER> with your correct path:

<PATH TO MAME FOLDER>/mame64 indy_6410 -cdrom <PATH TO MAME FOLDER>/roms/IRIX6.5ApplicationsJune1998.iso -harddisk <PATH TO MAME FOLDER>/roms/irix12gbHD.chd -window -nomaximize -resolution 1280x1024


You will see the Welcome to INDY screen, then a warning will say "unable to boot" press "continue" (probably means the HD has no system yet). You will then see the main CD-ROM interface with 6 buttons.

3) Click the Enter Command Monitor button.

enter:
setenv -f eaddr 08:00:69:12:34:56 <enter>
setenv monitor h <enter> (Tells system you have a high-res monitor)

Then click "done"

4) Enter Command Monitor again.

Initialize the HD. In Command Monitor type this command:

boot -f dksc(0,6,8)sashARCS dksc(0,6,7)stand/fx.ARCS


Then back to the Welcome screen, you can click "Install System Software". It will Say "Copying installation tools to disk"

It then loads the command monitor to ask permission to make a new file system on the hard disk.

Follow the prompts. It will ask you to choose Filesystem block size (I used "512")

After several minutes you will see "Invoking software installation." and a menu with 14 choices.

At the prompt Inst> type "6" <enter> for install. Press space bar to load all the text. You will see 4 choices. type "1" <enter> to install. It will ask if you want to check for old files type "no" <enter>

You will have a choice:

1/CDROM/dist
2/done

type "1" <enter> for install.

The installer will remind you that The CD-ROM is part of a set and prompt for insertion of other disc. You must insert the other discs one at a time using MAMEs internal UI "File Manager" to browse and select the disc(IRIX 6.5 Foundation 1.iso). Return to the machine by using the tab key and press Enter. The system will check the files and again prompt for any other discs. Use the File Manager again and load (IRIX 6.5 Foundation 2.iso). Do the same for (IRIX 6.5 Applications June 1998.iso).

At the inst> prompt type go <enter>

It should now start installing. Occasionally, it will ask you to insert another CD-ROM. Use MAMEs File Manager to insert the correct CD. Then return to the MAME machine and allow the installer to run.

I'm not sure how long it takes for this installation. I let MAME run in the background and just checked it every so often to see if it was asking for a different CD. Probably about 2 hours later the install was done.

At the inst> prompt type quit <enter>

You will see a notice "Requickstarting ELF files" a percentage will count to up to %100.

Do not be fooled by the word "quick". This process takes an hour.

Then the machine will reboot and you will be able to log into the GUI. So far I just used the "demos" account. No password is needed.

Usually it's a standard ATX or ITX case holding all that stuff and standard components like you'd buy to build your own PC.

Hmm... i think it should read

Do i need LLVM-7.1.0-win64.exe, the newer 8.x (only available as source) - or the one supplied by the Microsoft installer ("Clang C2 experimental") ?
Is it still Visual Studio 2017...?

My fellow countryman Rfka was also unable to build the solution, that's why i ask for a bit more details Thanks in advance.

Screenshot - mess.sln properties (VS 2017)
https://www.dropbox.com/s/lirblgiixwhvsr1/VS2017_Mess_platform_toolset.jpg?dl=0

The same guy I found at vcfed that provided the Hektor III ROMs, he happened to mention he had a 256 in bits on his bench and noticed our current dump was bad. He's been very helpful