Page 89 of 91

Posted: Mon 02 Jul, 2007 4:19 pm
by tr1p1ea
Im pretty sure this has been asked a few times, and probably the reason CoBB wrote the send utility. Its in the same dir as the latest PindurTI build :).

Posted: Mon 02 Jul, 2007 5:01 pm
by Timendus
Ah, yes, I forgot about that. I'll give it a try, but I doubt it's going to work with Wine...

Posted: Mon 02 Jul, 2007 5:14 pm
by NanoWar
Well, it *does* work with wine on my machine (suse 10.1)

Posted: Mon 02 Jul, 2007 5:37 pm
by GuillaumeH
The version of Wine matters more.

Posted: Mon 02 Jul, 2007 6:41 pm
by Jim e
Does everyone here use linux?

Posted: Mon 02 Jul, 2007 6:43 pm
by kv83
Jim e wrote:Does everyone here use linux?
No *raises hand for him and benryves* Windows FTW!

Posted: Mon 02 Jul, 2007 7:09 pm
by Liazon
no... does anyone use a mac?

Posted: Mon 02 Jul, 2007 8:02 pm
by Timendus
Wow, you're right... it works. Amazing.

And my PTI is running at a whopping average of 75% on my beautiful AMD Athlon64 3000+... That's just as bad as it used to be on my laptop. I'll see what I can do in the area of writing a GTK frontend for PTI...

Posted: Mon 02 Jul, 2007 11:36 pm
by Timendus
Okay, one evening later I got an interface with the PTI non-interactive linux build through two pipes and a simple but nicely native-Gnome-looking GUI that doesn't really do anything yet. No keypad of course, like the original. And I'm still far, FAR, from having such a lovely display emulation as the original. Or linking, or screenshotting, or...

Anyway, I plan to finish this up tomorrow (please let it be tomorrow :P) to the point where I can load a ROM image and some .8?? files, pass keyboard input to PTI, and I'll give a go at getting the PTI output in a Pixbuf. After that it's open source (even though it's crappy code) for anyone who wants to extend on it's functionality.

Posted: Tue 03 Jul, 2007 10:56 pm
by Andy_J
I see I'm a little late, but yeah everything worked fine for me with Darwine with one of the most recent version of Wine. :) (As evidenced on the previous page, anyway.)

Posted: Wed 04 Jul, 2007 12:24 am
by Timendus
Hmm, I'm gonna need a bit of help here from either CoBB or Ben...

I do the following:

Code: Select all

File selected: resources/TI-83.rom
Sending file...OK
Activating slot 0...OK
Running for 1000cc...OK
Pressing ON...OK
Running for 1000cc...OK
But my state dumps tell me that the screen is still off... Why is that? :) Am I too impatient with 1000 clockcycles?

Code: Select all

Dumping state lcd physics...OK
        Busy time min.: 25 cc
        Busy time max.: 47 cc
        Remains busy: 0 cc
        Momentum up: 15%
        Momentum down: 7%
        Contrast factor: 5%
        Op-amp factor: 15%
        White base level: 5%
        Black base level: 100%
        Current white: -65%
        Current black: 30%
Dumping state lcd software...OK
        Power: off
        Contrast: 18
        X-Address: 0
        Y-Address: 0
        Z-Address: 0
        Counter: Y, up
        Word length: 8
        Op-amps: amp1=0 amp2=0
        Test mode: off
        Dummy read: yes
Dumping state model...OK
        Model: TI-83 1.07
Dumping state time...OK
        Clock: 2008

Posted: Wed 04 Jul, 2007 12:41 am
by Jim e
Timendus wrote:But my state dumps tell me that the screen is still off... Why is that? :) Am I too impatient with 1000 clockcycles?
Yes

Thats only 1/6000th of a second. You need to press for about 1/2 a second and release and run for a bit longer.

Edit: You should probably give more boot up time than that to.

Posted: Wed 04 Jul, 2007 6:39 am
by CoBB
Yes, you should wait about half a second after resetting, then press on, then wait half a second or so and you can release it afterwards. Maybe you can get away with less, I guess there are differences between the models too.

Posted: Wed 04 Jul, 2007 11:53 am
by Timendus

Code: Select all

Sending file...OK
Activating slot 0...OK
Resetting the calculator...OK
Running for 6000000cc...OK
Pressing ON...OK
Running for 6000000cc...OK
Releasing ON...OK
Running for 6000000cc...OK
[...]
Dumping state lcd software...OK
        Power: off

Posted: Wed 04 Jul, 2007 11:00 pm
by Timendus
Okay, I figure I owe the rest of the board an update :)

It took CoBB and me about a dozen private messages and a lot of patience to find out that the linux non-interactive build that's on the PTI website is actually broken. It'll never turn the screen on. Once that was clear I tried to recompile a new version of the linux non-interactive build from the original source, but that gave me exactely the same result. So that pretty much got me nowhere. Now I'm just hoping that CoBB will come up with a brilliant idea.

But I've been using the Windows version in non-interactive mode through Wine (talking about an ugly hack :)) to develop my front-end, and it's getting together. Here's a screenshot of the first "Mem cleared" ;)

Image

It emulates a screen, with more or less as pretty looks as the original (though I still have to properly fix an ugly signed/unsigned int error, what you're seeing here is the yucky workaround). It updates the screen 25 times a second, which is the maximum greyscale output frequency of the PTI back-end, and it has the emulator run the corresponding number of clockcycles on every update. In other words; you can see the cursor flashing at the proper speed :)

Interface-wise you can load a ROM image and .8?? files through a fancy file browse interface (Emulator -> Open -> "ROM image" or "Program/Group", can't take a screenshot of that for some reason, so you'll have to take my word for it), you can make the program dump it's status to the command line and you can type in keys which will be passed on to PTI. I still have to add a few more keys though to make it useful :)

It depends on libgtkmm and it should run nicely under Gnome and KDE.

Now the only serious problem is to get a native Linux build that works properly... :( Otherwise this little program doesn't really solve any problem...