I am running 10.4.11 on a PowerBook G4, and attempting to launch
retro.py. Depending on the specific image I symlink to, I either get
a quiet exit, with exit code 0 (retroImage, retroImage64,
retroImage64BE, retroImageBE), or a noisy exit w/exit code 1
(retroImage16, retroImage16BE).
In the noisy case, here's the error message:
====
Traceback (most recent call last):
File "/Users/jmc/bin/retro.py", line 427, in <module>
run()
File "/Users/jmc/bin/retro.py", line 400, in run
memory = list(struct.unpack( cells * 'i', f.read() ))
struct.error: unpack requires a string argument of length 13936
====
The file sizes might have a bearing on this, but none of the images is
13936. The two that are closest are the ones that produce the noisy
failures:
-rw-r--r-- 1 jmc jmc 55752 Aug 12 14:46 retroImage64
-rw-r--r-- 1 jmc jmc 55752 Aug 12 14:46 retroImage64BE
-rw-r--r-- 1 jmc jmc 27876 Aug 12 14:47 retroImageBE
-rw-r--r-- 1 jmc jmc 27876 Aug 12 10:04 retroImage
-rw-r--r-- 1 jmc jmc 13938 Aug 12 10:05 retroImage16
-rw-r--r-- 1 jmc jmc 13938 Aug 12 10:06 retroImage16BE
This looks like a very basic problem, which could be difficult to fix,
or completely trivial. Do the symptoms I describe indicate what the
problem is, and what I can do about it?
-jmc
> --
> --
> You received this message because you are RETRO 10 discussion group.
> To post to this group, send email to
retr...@googlegroups.com
> To unsubscribe from this group, send email to
>
retro-10-u...@googlegroups.com