Comments on: VenturComm Venix/86 on MESS/MAME

By: bbslovag

bbslovag — Thu, 03 Jan 2019 11:00:12 +0000

user@errorlevel:0:~/mess/roms/at386$ for i in ck md5 sha1;do echo “$i”sum:;$i”sum” *;done
cksum:
3709130015 65536 ami386.bin
1499440492 65536 amicg.1
580287451 65536 at386.bin
md5sum:
429709863d4770540a0db5c463a01e7c ami386.bin
f1f2272ca9ead3b2a83c49f7ad6b712b amicg.1
d4a6cfdfd6334e0a6a42356424cebd28 at386.bin
sha1sum:
8289ba36a3dfc3324333b1a834bc6b0402b546f0 ami386.bin
9893d3ac851e01b06a68a67d3721df36ca2c96f5 amicg.1
def71567dee373dc67063f204ef44ffab9453ead at386.bin

By: Helge Skrivervik

Helge Skrivervik — Thu, 18 Feb 2016 16:59:58 +0000

Thanks Tenox and Jim – you got an old Venix user/developer started again, with Venix86 running on a Compaq portable III (286).
I’d love to get it running on MAME (mac, no pc’s in sight except for the compaq). MAME64 runs but the ROM files (for at386) are missing. Any hints as to where to find them?

Helge S

By: dank moo

dank moo — Fri, 25 Dec 2015 23:27:52 +0000

In reply to geophoto. Nothing. Do it anyway.

By: geophoto

geophoto — Sat, 22 Aug 2015 01:34:04 +0000

I am unable to get the at386 system to work – I have located the roms, but the system lists as “not working” – what am I doing wrong?

By: Rainbow

Rainbow — Mon, 17 Aug 2015 01:10:17 +0000

In reply to neozeed.

That’s really awesome!

Until there is a way to port better SLiRP networking support from Cocktrice to PCem, I’m pretty much gonna stick to Virtual PC where I’m currently multi-booting MS-DOS 6.22, OS/2, Windows 95 OSR2 and Puppy Linux. 🙂

When running Windows 95 OSR2 under Virtual PC 2007, I can infact run Basilisk II by linking the hard disk images in a folder-shared directory.

By: neozeed

neozeed — Sun, 16 Aug 2015 22:54:48 +0000

In reply to Rainbow. Well that is why I started cockatrice, which started by gutting out the win32 support as it is... VERY win32 which was all great for NT 4/98 and replacing it with being more SDL. And I gutted a bunch of crazy 'features' to try to make it more stable. I can actually run Internet Explorer 3 and 4, while they instantly explode Basilisk II. I have that mini fork of Sheep which I added winpcap to, and it works well enough for me to mount apple shares, and again use web browsers. So it's good enough for me. I keep them 32 bit, as they seem to be more stable in that setting. Especially since they started out as 32bit programs, with the heart of Basilisk being UAE, the Amiga emulator.

By: Rainbow

Rainbow — Sun, 16 Aug 2015 22:16:13 +0000

In reply to neozeed. That's what I've been thinking. Some of the features in Basilisk II don't work in 64-bit Windows as it not been updated to support 64-bit Windows in a long time. Basilisk II does work on OSes as early as Windows 95.

By: neozeed

neozeed — Sun, 16 Aug 2015 21:56:26 +0000

In reply to Federico Bianchi. Am I the only one that can use winpcap on Windows 10 just fine?

By: neozeed

neozeed — Sun, 16 Aug 2015 21:55:36 +0000

In reply to Rainbow. basilisk is pointless to be 64bit. it works great as 32bit, esp my fork where networking actually works.

By: Rainbow

Rainbow — Sun, 16 Aug 2015 20:41:15 +0000

In reply to neozeed.

That sounds like fun! 😀 The only problem is that networking support under Basillisk II doesn’t work on 64-bit versions of Windows (including Windows Vista).

Neozeed, if you have SLiRP networking support fully working under PCem with a networking patch, I would love to see it so that I can pass it along in the PCem Developement forum.

For network drives and folder sharing, I bet that TUN/TAP interface such as OpenVPN is required for it to work.

For SLiRP networking, Winpcap and a host network interface is not required as well as I know. The problem is that Winpcap hasn’t been updated since 2013 which is a real bummer.