Reply
Thread Tools
smileyninja's Avatar
Posts: 24 | Thanked: 0 times | Joined on Jul 2007 @ Lakeland, FL
#61
Some more free apps:

The DiskTools Collection (look at the bottom of the page) http://www.rainmakerinc.com/download...downloads.html

A couple of software download sites:
http://www.pure-mac.com/

http://download.nafura.it/home/mac/index.asp

http://hyperarchive.lcs.mit.edu/HyperArchive.html

Last edited by smileyninja; 2008-02-12 at 01:42.
 
tobiasj's Avatar
Posts: 241 | Thanked: 74 times | Joined on Jul 2007
#62
Originally Posted by t3h View Post
I'll add a prefs key and a commandline for fullscreen mode. I originally had it going in fullscreen all the time.

As for a GUI icon, take a look at other .desktop files that launch things, and add the appropriate lines.
Thanks! That will be great..

I thought of that already, and looked at a couple, but nothing really jumped out at me, I was hoping someone knew what it would take. I will look again at a couple more .desktop files.

Thanks again!

-John
 
Posts: 156 | Thanked: 44 times | Joined on Dec 2007
#63
There's now a prefs option for "fullscreen" - you can start it up with either ./BasiliskII --fullscreen true or add "fullscreen true" to your /home/user/.basilisk_ii_prefs file.

Binary (+ .desktop file): http://gm.stackunderflow.com/maemo/b...ary_0.3.tar.gz

Sources (now slightly smaller after removing a bit of code for other platforms)
http://gm.stackunderflow.com/maemo/b...emo_0.3.tar.gz

Last edited by t3h; 2008-02-12 at 02:27.
 

The Following 4 Users Say Thank You to t3h For This Useful Post:
taguapire's Avatar
Posts: 107 | Thanked: 14 times | Joined on Dec 2007
#64
Hi,

I don't know what is happening but I'm getting the following message:
Code:
Basilisk II V0.9 by Christian Bauer et al.
ERROR: Cannot open ROM file.
How I can fix it?

Regards,

Taguapire.

BTW: I'm using the same rom file with BasiliskII on my Mac.
 
Posts: 156 | Thanked: 44 times | Joined on Dec 2007
#65
Ensure that you have your prefs file pointing to the right place, otherwise start it up with --rom /path/to/rom.

If you want to make a new disk, and don't know how:
Code:
dd if=/dev/zero of=b2_2.img bs=40M count=1
will create an empty file of that size.

Last edited by t3h; 2008-02-12 at 05:45.
 
debernardis's Avatar
Posts: 2,142 | Thanked: 2,054 times | Joined on Dec 2006 @ Sicily
#66
In the TODO list there should be also a way to use the n810 hardware keyboard. Presently, with 'keycodes false' in the prefs file, the blue chars (i.e. those you get with the Fn key) are not recognized.
I tried to set 'keycodes true' but nothing seems to change, either in the keyboard layout or in the effect of the fn key. Maybe because I had no keycode translation file at hand?
 
Posts: 156 | Thanked: 44 times | Joined on Dec 2007
#67
Originally Posted by debernardis View Post
In the TODO list there should be also a way to use the n810 hardware keyboard. Presently, with 'keycodes false' in the prefs file, the blue chars (i.e. those you get with the Fn key) are not recognized.
I tried to set 'keycodes true' but nothing seems to change, either in the keyboard layout or in the effect of the fn key. Maybe because I had no keycode translation file at hand?
I don't have a N810, so I can't help there...

Supply a keycodes file and point to it with keycodes <keycodefile>, and see what happens.
 
tobiasj's Avatar
Posts: 241 | Thanked: 74 times | Joined on Jul 2007
#68
Originally Posted by taguapire View Post
Hi,

I don't know what is happening but I'm getting the following message:
Code:
Basilisk II V0.9 by Christian Bauer et al.
ERROR: Cannot open ROM file.
How I can fix it?

Regards,

Taguapire.

BTW: I'm using the same rom file with BasiliskII on my Mac.
I had the same problem with mine until I figured out that I couldn't put both the executable and the prefs in the same folder. I put the prefs in /home/user and the exec in /usr/sbin and launch it using a custom .desktop file that creates an icon in extras in the start menu.. (attached, remove.txt from the end of the filename and put in /usr/share/applications/hildon)



-John
Attached Files
File Type: txt basiliskii.desktop.txt (206 Bytes, 408 views)
 
Posts: 156 | Thanked: 44 times | Joined on Dec 2007
#69
For the next version, I'll look at some GTK error boxes (instead of console errors), and after that's done, I'll make a .deb package with .desktop and binary.

At the moment, if you launch it from a .desktop file and something goes wrong - you'll never know what. Which is slightly annoying when you've just installed it and don't know what's wrong.
 
tobiasj's Avatar
Posts: 241 | Thanked: 74 times | Joined on Jul 2007
#70
Originally Posted by t3h View Post
For the next version, I'll look at some GTK error boxes (instead of console errors), and after that's done, I'll make a .deb package with .desktop and binary.

At the moment, if you launch it from a .desktop file and something goes wrong - you'll never know what. Which is slightly annoying when you've just installed it and don't know what's wrong.
Thats very true, though it certainly wouldn't be the first time lol...

I agree until you have it working the way you want it, launch it from xterm so you can see what is going on. Plus as you tweak the settings it is easier to use the switches than to keep editing the prefs file, and if you launch it from xterm you dont have to wait for it to boot to shut it down, you can just CTRL-C it and poof!

Great app, great port, thanks for all the effort, it makes the NIT just that much more indispensable to me..

-John
 
Reply


 
Forum Jump


All times are GMT. The time now is 14:11.