Previous Thread
Next Thread
Print Thread
Page 4 of 5 1 2 3 4 5
Re: Problem with Coco emulation and cartslot [Re: Robert Gault] #64944
10/11/10 01:36 AM
10/11/10 01:36 AM
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
T
tlindner Offline
Senior Member
tlindner  Offline
Senior Member
T
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
cartslot.c seems to be where the pcb type of the ROM is matched against the available PCB types.

But the problem is the PCB type is never set. Nothing in cartslot.c will ask the hashfile for the PCB type.

I am a little stumped on how all this is suppose to work.


tim lindner
tlindner@macmess.org
Re: Problem with Coco emulation and cartslot [Re: tlindner] #64947
10/11/10 03:50 AM
10/11/10 03:50 AM
Joined: Jan 2006
Posts: 3,687
Trondheim, Norway
etabeta78 Offline
Very Senior Member
etabeta78  Offline
Very Senior Member
Joined: Jan 2006
Posts: 3,687
Trondheim, Norway
being coco-specific, I would expect the code to be in coco_crt.c and image.extrainfo() being involved (since the latter is the function which accesses the hsi files, looking for info)

Re: Problem with Coco emulation and cartslot [Re: etabeta78] #64949
10/11/10 04:16 AM
10/11/10 04:16 AM
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
T
tlindner Offline
Senior Member
tlindner  Offline
Senior Member
T
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
I disagree, this seems to be a cartslot.c problem. On line 361 image.pcb() is called but always contains empty information.

Now if I add a image.crc(); call before line 361, the hash file is queried and everything starts working.

So either it is a bug for a device_image_interface object to be created without filling in the meta fields -or- it is a bug to query the meta information before forcing their loading.


tim lindner
tlindner@macmess.org
Re: Problem with Coco emulation and cartslot [Re: Robert Gault] #64952
10/11/10 05:17 AM
10/11/10 05:17 AM
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
T
tlindner Offline
Senior Member
tlindner  Offline
Senior Member
T
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
OK, I just test booting RGBDOS and it worked. Here is the patch:
Code:
--- src/mess/devices/cartslot.c	(revision 9357)
+++ src/mess/devices/cartslot.c	(working copy)
@@ -358,6 +358,7 @@
 			if (image.pcb() != NULL)
 			{
 				/* read from hash file */
+				image.crc();
 				astring_cpyc(&pcb_name, image.pcb());
 			}
 		}

I also added the following to the hsi file
Code:
--- hash/coco.hsi	(revision 9357)
+++ hash/coco.hsi	(working copy)
@@ -518,6 +518,9 @@
   <hash crc32="7f0edf28" sha1="6ca61e29c136ec8201492ca7f9eb050912f3582d" name="Extended ADOS">
     <pcb>coco_fdc</pcb>
   </hash>
+  <hash crc32="bdd25664" name="RGBDOS">
+    <pcb>coco_fdc</pcb>
+  </hash>
   <hash crc32="d990e1f9" name="RS-232 Pak">
     <pcb>rs232</pcb>
   </hash>

I'm not sure if this if the final patch, hopefully someone who knows will get back to me about my question in the previous message.


tim lindner
tlindner@macmess.org
Re: Problem with Coco emulation and cartslot [Re: tlindner] #64956
10/11/10 02:03 PM
10/11/10 02:03 PM
Joined: Dec 2007
Posts: 301
Michigan
R
Robert Gault Offline OP
Senior Member
Robert Gault  Offline OP
Senior Member
R
Joined: Dec 2007
Posts: 301
Michigan
Tim,

Your correction to src/mess/devices/cartslot.c works for me. I have been able to get floppy I/O and realtime clock I/O with RGBDOS. I have also been able to mount both ADOS3 and Extended ADOS3 and get disk I/O.

One point that should be given consideration. There will be many custom versions of ADOS because you can generate custom versions of the ROM as part of the software. There are also at least two versions of RGBDOS on the web which differ in the masks for the $FF40 disk values.
That means the CRC32 and SHA1 values will be different for all of these versions. Mounting these roms in the cartslot will fail with the .hsi file containing incorrect CRC values. Therefore all MESS coco users should determine the appropriate CRCs and customize the coco.hsi file.

I have not yet tested the RS-232 pak or the Speech/Sound pak but will report later on these two units.

Re: Problem with Coco emulation and cartslot [Re: Robert Gault] #64957
10/11/10 02:17 PM
10/11/10 02:17 PM
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
T
tlindner Offline
Senior Member
tlindner  Offline
Senior Member
T
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
Don't bother with the S/SC. It is completely commented out.


tim lindner
tlindner@macmess.org
Re: Problem with Coco emulation and cartslot [Re: tlindner] #64958
10/11/10 05:57 PM
10/11/10 05:57 PM
Joined: Dec 2007
Posts: 301
Michigan
R
Robert Gault Offline OP
Senior Member
Robert Gault  Offline OP
Senior Member
R
Joined: Dec 2007
Posts: 301
Michigan
I'm not sure what to expect from the RS232.ROM. It will boot in the cartslot but I can't communicate with a Coco3 running Ultimaterm over a serial cable regardless of settings.

Will the ROM actually connect to a PC serial port or is that portion of the code not working?

Re: Problem with Coco emulation and cartslot [Re: Robert Gault] #64962
10/12/10 12:19 AM
10/12/10 12:19 AM
Joined: Dec 1999
Posts: 1,170
Vancouver Island, BC, Canada
J
Justin Offline
Very Senior Member
Justin  Offline
Very Senior Member
J
Joined: Dec 1999
Posts: 1,170
Vancouver Island, BC, Canada
MESS has no ability to interface with physical serial ports.

Re: Problem with Coco emulation and cartslot [Re: Justin] #64980
10/12/10 10:30 PM
10/12/10 10:30 PM
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
T
tlindner Offline
Senior Member
tlindner  Offline
Senior Member
T
Joined: Feb 2000
Posts: 207
SF Bay Area, CA, USA
Has any one had any luck using SDLMESS with named pipes (fifos) on *nix? I couldn't find a terminal program that allowed I/O thru a named pipe. I tried screen and cu, but they only wanted to talk thru something in /dev.

If I can get that working, then it is a small jump to use and named pipe and netcat.


tim lindner
tlindner@macmess.org
Re: Problem with Coco emulation and cartslot [Re: tlindner] #64982
10/12/10 11:30 PM
10/12/10 11:30 PM
Joined: Mar 2001
Posts: 16,206
USA
R
R. Belmont Online content
Very Senior Member
R. Belmont  Online Content
Very Senior Member
R
Joined: Mar 2001
Posts: 16,206
USA
I think the SDL OSD uses a named pipe in /tmp to route the MAME outputs (e.g. cabinet lamps and stuff - on Windows it uses window messages). There's no support on anything for routing serial or parallel ports out of MESS that I'm aware of.

Page 4 of 5 1 2 3 4 5

Who's Online Now
2 registered members (Dam0, reenigne), 28 guests, and 3 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,654
Posts113,414
Members4,846
Most Online324
Dec 20th, 2018
Powered by UBB.threads™ PHP Forum Software 7.6.1.1
(Release build 20180111)
Page Time: 0.055s Queries: 15 (0.013s) Memory: 5.7269 MB (Peak: 5.9502 MB) Zlib enabled. Server Time: 2019-05-26 06:59:39 UTC