Puppy Arcade 7
sc0ttman
I've sorted the keyboard problem with Frodo C64 emulation.
I had got too focused on the Vice C64 emulation keyboard. This uses the # key (UK keyboard) for the C64 = key. I thought the same would work with Frodo but it just did nothing. With a US keymap loaded it actually gave a ^, but I don't think this key is available on a real US keyboard. We Brits seem to have an extra key.
Anyway, tonight I found that Page Down gives the C64 = key whether a UK or US keymap is used.
There is no need to include this info in a help file. I finally found the help files for Frodo in Puppy Arcade 7, especially:
/usr/local/Frodo-4.1b-US/docs/keyboard.html
The keyboard seems to be as quoted for BeOS (not Unix, strangely, where Page Up gives something different).
Users of Frodo would do well to read the settings.html file in the same directory, especially the limit speed setting. With the default the speed was racing away with constant noise from something internal to my laptop. As soon as I ticked limit speed I got a normal speed flashing cursor and the internal noise stopped!
If there needs to be anything extra in Puppy Arcade 8, maybe it should be a reference to the location of the Frodo Help files. I only found them by tracing back from /usr/bin/frodo via its properties to /usr/local/bin/frodo which I discovered was a shell script so opened it as a text file. This showed me the esistence of /usr/local/Frodo-4.1b-US and the rest was easy. I don't think a noob would find these help files!
The help on the launcher menu points at General Puppy Help and not the Arcade help. Maybe this should be improved.
Now I can have some fun and relive the C-64 days!
I've sorted the keyboard problem with Frodo C64 emulation.
I had got too focused on the Vice C64 emulation keyboard. This uses the # key (UK keyboard) for the C64 = key. I thought the same would work with Frodo but it just did nothing. With a US keymap loaded it actually gave a ^, but I don't think this key is available on a real US keyboard. We Brits seem to have an extra key.
Anyway, tonight I found that Page Down gives the C64 = key whether a UK or US keymap is used.
There is no need to include this info in a help file. I finally found the help files for Frodo in Puppy Arcade 7, especially:
/usr/local/Frodo-4.1b-US/docs/keyboard.html
The keyboard seems to be as quoted for BeOS (not Unix, strangely, where Page Up gives something different).
Users of Frodo would do well to read the settings.html file in the same directory, especially the limit speed setting. With the default the speed was racing away with constant noise from something internal to my laptop. As soon as I ticked limit speed I got a normal speed flashing cursor and the internal noise stopped!
If there needs to be anything extra in Puppy Arcade 8, maybe it should be a reference to the location of the Frodo Help files. I only found them by tracing back from /usr/bin/frodo via its properties to /usr/local/bin/frodo which I discovered was a shell script so opened it as a text file. This showed me the esistence of /usr/local/Frodo-4.1b-US and the rest was easy. I don't think a noob would find these help files!
The help on the launcher menu points at General Puppy Help and not the Arcade help. Maybe this should be improved.
Now I can have some fun and relive the C-64 days!
I think I love you... hahaha..
But great stuff once again... I REALLY appreciate the work you've done with Puppy Arcade..
You are helping to improve it more than me!! : .. D
Last edited by sc0ttman on Wed 10 Mar 2010, 06:36, edited 1 time in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Good man! I pressed every key to see what they did, but having never used a commodre (they're a bit before my time) I couldn't really tell what I was doing!!!ICPUG wrote:sc0ttman
I've sorted the keyboard problem with Frodo C64 emulation... I found that Page Down gives the C64 = key, whether a UK or US keymap is used.
Agreed.. Frodo was left in as an 'after-thought' - so people don't need to hunt for C64 BIOS... I'll make sure ALL emulator help files are easily found..ICPUG wrote:If there needs to be anything extra in Puppy Arcade 8, maybe it should be a reference to the location of the Frodo Help files.
Indeed.. I was worried that removing the default help pages would annoy a few people - especially as, unlike many other puplets, Puppy Arcade tends to attract a lot of first time Puppy users....ICPUG wrote:The help on the launcher menu points at General Puppy Help and not the Arcade help. Maybe this should be improved.
But I'll create a new HTML page with links to all the original puppy help, plus the emulator help files and so on... I've recently tested Puppy 4.4 actually, and would like to steal a few ideas on this subject...
Enjoy!ICPUG wrote:Now I can have some fun and relive the C-64 days!
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
I found gngeo of a new version here.
http://puppy.cnbits.com
However, because it will not have been possible to open it to the public the way things are going, it regenerated a little.
http://puppy.cnbits.com
However, because it will not have been possible to open it to the public the way things are going, it regenerated a little.
I'll add some screenshot once I've tested it.Nikukyu wrote:I found gngeo of a new version here.
http://puppy.cnbits.com
However, because it will not have been possible to open it to the public the way things are going, it regenerated a little.
You're welcome,sc0ttmansc0ttman wrote:But great stuff once again... I REALLY appreciate the work you've done with Puppy Arcade..
You are helping to improve it more than me!! : .. D
But, though it only has to be able to help a little more.
Thank you very much by all means, kandkyokandkyo wrote:I'll add some screenshot once I've tested it.
In addition, I found gelide-0.1.3 deb file.
It will up-load it with the tgz file later.
Whether it operates cannot be judged.
Hi folks,
Myself and some colleagues have just put together a DIY arcade cabinet ( wooden framework, TV, PC with PuppyLinux and SDLMame PET addition installed auto-loading-at-boot, VGA to Scart box, and a custom control panel via a USB connected board ).
I did a lot of searching for a good USB install and finally found PuppyLinux ( I had tried a DOS install, but couldn't find a DOS MAME page that was still live!!! )
I'm using PuppyLinux booted of a USB pen drive.
Many thanks to the PuppyArcade devs / organisers btw!!!
There are a few questions I'd like to ask ( I'm fairly new to Linux etc ).
- At the moment, I have SDLMame auto-starting on boot-up. However, it seems to start in an X bordered window ( without keyboard control but with joystick control ). If a game is selected with the joystick, then it becomes full-screen. If the window is clicked on with a mouse, it becomes full-screen.
The question here is - how can I force SDLMame to start at start-up, and remain full-screen in the Puppy Linux distro?
- How do people sync the TV up with eg scrolling games, in order to reduce the screen tearing? Is this an X thing, or does SDLMame over-ride X ( and allow frame synching etc )? ( or any of the other apps shipped with Puppy Linux )
Now, the most important question
- When I quit SDLMame ( I have it set up to auto-save states ), I can view a previously stored high-score. If I then turn off the power ( ie no shutdown - the cabinet is going to eventually be self contained ), and reload the OS -> SDLMame, the scores don't seem to be saved - almost as if the state was cached, and this cache wasn't saved to the USB drive.
Is there any way to have it so that, if an app such as SDLMame saves information within a running Puppy Linux instance, it is saved for the next reload - even if it is a hard restart?
Thanks in advance for any help here - we're amazed that we got so far with the arcade cabinet and are enjoying it in its current setup, but being able to fix these small issues would be the icing on the cake!!!
Mal
Myself and some colleagues have just put together a DIY arcade cabinet ( wooden framework, TV, PC with PuppyLinux and SDLMame PET addition installed auto-loading-at-boot, VGA to Scart box, and a custom control panel via a USB connected board ).
I did a lot of searching for a good USB install and finally found PuppyLinux ( I had tried a DOS install, but couldn't find a DOS MAME page that was still live!!! )
I'm using PuppyLinux booted of a USB pen drive.
Many thanks to the PuppyArcade devs / organisers btw!!!
There are a few questions I'd like to ask ( I'm fairly new to Linux etc ).
- At the moment, I have SDLMame auto-starting on boot-up. However, it seems to start in an X bordered window ( without keyboard control but with joystick control ). If a game is selected with the joystick, then it becomes full-screen. If the window is clicked on with a mouse, it becomes full-screen.
The question here is - how can I force SDLMame to start at start-up, and remain full-screen in the Puppy Linux distro?
- How do people sync the TV up with eg scrolling games, in order to reduce the screen tearing? Is this an X thing, or does SDLMame over-ride X ( and allow frame synching etc )? ( or any of the other apps shipped with Puppy Linux )
Now, the most important question
- When I quit SDLMame ( I have it set up to auto-save states ), I can view a previously stored high-score. If I then turn off the power ( ie no shutdown - the cabinet is going to eventually be self contained ), and reload the OS -> SDLMame, the scores don't seem to be saved - almost as if the state was cached, and this cache wasn't saved to the USB drive.
Is there any way to have it so that, if an app such as SDLMame saves information within a running Puppy Linux instance, it is saved for the next reload - even if it is a hard restart?
Thanks in advance for any help here - we're amazed that we got so far with the arcade cabinet and are enjoying it in its current setup, but being able to fix these small issues would be the icing on the cake!!!
Mal
Hi folks,
Myself and some colleagues have just put together a DIY arcade cabinet ( wooden framework, TV, PC with PuppyLinux and SDLMame PET addition installed auto-loading-at-boot, VGA to Scart box, and a custom control panel via a USB connected board ).
I did a lot of searching for a good USB install and finally found PuppyLinux ( I had tried a DOS install, but couldn't find a DOS MAME page that was still live!!! )
I'm using PuppyLinux booted of a USB pen drive.
Many thanks to the PuppyArcade devs / organisers btw!!!
There are a few questions I'd like to ask ( I'm fairly new to Linux etc ).
- At the moment, I have SDLMame auto-starting on boot-up. However, it seems to start in an X bordered window ( without keyboard control but with joystick control ). If a game is selected with the joystick, then it becomes full-screen. If the window is clicked on with a mouse, it becomes full-screen.
The question here is - how can I force SDLMame to start at start-up, and remain full-screen in the Puppy Linux distro?
- How do people sync the TV up with eg scrolling games, in order to reduce the screen tearing? Is this an X thing, or does SDLMame over-ride X ( and allow frame synching etc )? ( or any of the other apps shipped with Puppy Linux )
Now, the most important question
- When I quit SDLMame ( I have it set up to auto-save states ), I can view a previously stored high-score. If I then turn off the power ( ie no shutdown - the cabinet is going to eventually be self contained ), and reload the OS -> SDLMame, the scores don't seem to be saved - almost as if the state was cached, and this cache wasn't saved to the USB drive.
Is there any way to have it so that, if an app such as SDLMame saves information within a running Puppy Linux instance, it is saved for the next reload - even if it is a hard restart?
Thanks in advance for any help here - we're amazed that we got so far with the arcade cabinet and are enjoying it in its current setup, but being able to fix these small issues would be the icing on the cake!!!
Mal
Myself and some colleagues have just put together a DIY arcade cabinet ( wooden framework, TV, PC with PuppyLinux and SDLMame PET addition installed auto-loading-at-boot, VGA to Scart box, and a custom control panel via a USB connected board ).
I did a lot of searching for a good USB install and finally found PuppyLinux ( I had tried a DOS install, but couldn't find a DOS MAME page that was still live!!! )
I'm using PuppyLinux booted of a USB pen drive.
Many thanks to the PuppyArcade devs / organisers btw!!!
There are a few questions I'd like to ask ( I'm fairly new to Linux etc ).
- At the moment, I have SDLMame auto-starting on boot-up. However, it seems to start in an X bordered window ( without keyboard control but with joystick control ). If a game is selected with the joystick, then it becomes full-screen. If the window is clicked on with a mouse, it becomes full-screen.
The question here is - how can I force SDLMame to start at start-up, and remain full-screen in the Puppy Linux distro?
- How do people sync the TV up with eg scrolling games, in order to reduce the screen tearing? Is this an X thing, or does SDLMame over-ride X ( and allow frame synching etc )? ( or any of the other apps shipped with Puppy Linux )
Now, the most important question
- When I quit SDLMame ( I have it set up to auto-save states ), I can view a previously stored high-score. If I then turn off the power ( ie no shutdown - the cabinet is going to eventually be self contained ), and reload the OS -> SDLMame, the scores don't seem to be saved - almost as if the state was cached, and this cache wasn't saved to the USB drive.
Is there any way to have it so that, if an app such as SDLMame saves information within a running Puppy Linux instance, it is saved for the next reload - even if it is a hard restart?
Thanks in advance for any help here - we're amazed that we got so far with the arcade cabinet and are enjoying it in its current setup, but being able to fix these small issues would be the icing on the cake!!!
Mal
firstly, that sounds great, I'd love to see a simple 'how to'..mal wrote:Hi folks,
Myself and some colleagues have just put together a DIY arcade cabinet ( wooden framework, TV, PC with PuppyLinux and SDLMame PET addition installed auto-loading-at-boot, VGA to Scart box, and a custom control panel via a USB connected board ).
I'm don't have MAMPGUI installed at the moment, and I'm not even on Puppy, but you can type 'mamepgui -help' to see all the help options for it.. There should be something there to help.. Also MAME in general is better when using 'Xvideo (Left Alt+Home)' ((I think))....mal wrote:The question here is - how can I force SDLMame to start at start-up, and remain full-screen in the Puppy Linux distro?
'Vsync' is the option that is designed to match the refreshing of the display hardware and the emulator itself. This may or may not help..mal wrote:How do people sync the TV up with eg scrolling games, in order to reduce the screen tearing?
Using the command 'save2flash' will do this.. This can be setup to run automatically every 30 mins (which is the puppy default)..mal wrote:Is there any way to have it so that, if an app such as SDLMame saves information within a running Puppy Linux instance, it is saved for the next reload - even if it is a hard restart?
Go to "menu->system->puppy event manager->save session" and set the interval to 30
[you can run 'snapmergepuppy' n the terminal, too - this will also update your save file]
Puppy Arcade will already ask you if you want to save to a file when you shutdown (properly) but if you just unplug the machine, then it wont, so you will probably need to use the mathod shown above.
You're welcome.. Hope this stuff helps..mal wrote:Thanks in advance for any help here - we're amazed that we got so far with the arcade cabinet and are enjoying it in its current setup, but being able to fix these small issues would be the icing on the cake!!!
Mal
Last edited by sc0ttman on Wed 07 Apr 2010, 05:52, edited 1 time in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Firefox for puppy: http://www.murga-linux.com/puppy/viewtopic.php?t=30434..
Or try firedog (see link below this text) - it was built for puplets that have no office suite, like Puppy Arcade..
Or try firedog (see link below this text) - it was built for puplets that have no office suite, like Puppy Arcade..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Ok thanks, couple more questions. This DOSBox frontend leave much to be desired. It only give me 3 choices of fullscreen res and won't go down low enough to actually get my DOS games to be fullscreen, they always have a rather large black boarder.
My other question is how to I customize the wbar to make my own lauchers or for instance if I click on the DOS launcher in the navigation bar how do I set the properties to start another frontend beside the one it's currently using?
My other question is how to I customize the wbar to make my own lauchers or for instance if I click on the DOS launcher in the navigation bar how do I set the properties to start another frontend beside the one it's currently using?
For DOSBox, open DOSBoxGUI and just choose 'Output=overlay' and your fullscreen display will stretch to fit the screen...rfxcasey wrote:Ok thanks, couple more questions. This DOSBox frontend leave much to be desired. It only give me 3 choices of fullscreen res and won't go down low enough to actually get my DOS games to be fullscreen, they always have a rather large black boarder.
My other question is how to I customize the wbar to make my own lauchers or for instance if I click on the DOS launcher in the navigation bar how do I set the properties to start another frontend beside the one it's currently using?
On any resolution..
About wbar:
Use the wbarcc, found in "Menu->Desktop->Wbar - configuration centre"... This tool allows you to easily manage wbar..
Or, you could also just open "/root/.wbar" in a text editor, and manually edit the line that sayd "c:dosboxgui", which should be on line 34...
You can change the command 'dosboxgui' to whatever you like...
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
I have the same problem: my USB thumb-drives don't work, but I can see them form the hardware list (it may be under "System", but I am not sure).
By the way: last time I used Puppy Arcade was soon after its first release, a few days ago I looked for some updates and I've seen that now there is the 7th version! That's cool, I tried it and I like it very much!
Congratulations sc0ttman!
By the way: last time I used Puppy Arcade was soon after its first release, a few days ago I looked for some updates and I've seen that now there is the 7th version! That's cool, I tried it and I like it very much!
Congratulations sc0ttman!
USB Thumb Drives
[edit] Forgot to say, welcome back, Feel, hope you like the latest version! Version 8 will be even better!
About USB Drives:
MuppyQuickMount is the default mounting tool in Puppy Arcade because it's very fast and convenient.. However..
Sometimes, MuppyQuickMount cannot mount devices which normally work in Puppy. In these cases, I've found that using Pmount, the regular mounting tool that is installed as default in most Puppies, works fine..
To use a Pmount instead, go to "Menu->FileSystem->Pmount"..
You can also replace the command in "~/.jwm-apps", then restart JWM, so that Pmount is used when you click 'Drives', in the apps menu..
About USB Drives:
MuppyQuickMount is the default mounting tool in Puppy Arcade because it's very fast and convenient.. However..
Sometimes, MuppyQuickMount cannot mount devices which normally work in Puppy. In these cases, I've found that using Pmount, the regular mounting tool that is installed as default in most Puppies, works fine..
To use a Pmount instead, go to "Menu->FileSystem->Pmount"..
You can also replace the command in "~/.jwm-apps", then restart JWM, so that Pmount is used when you click 'Drives', in the apps menu..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Re: USB Thumb Drives
I did EXACTLY like you said but I still can only see my USB drives in the hardware list. However after doing a complete reinstall I finally got the USB working. It's a miracle.sc0ttman wrote:[edit] Forgot to say, welcome back, Feel, hope you like the latest version! Version 8 will be even better!
About USB Drives:
MuppyQuickMount is the default mounting tool in Puppy Arcade because it's very fast and convenient.. However..
Sometimes, MuppyQuickMount cannot mount devices which normally work in Puppy. In these cases, I've found that using Pmount, the regular mounting tool that is installed as default in most Puppies, works fine..
To use a Pmount instead, go to "Menu->FileSystem->Pmount"..
You can also replace the command in "~/.jwm-apps", then restart JWM, so that Pmount is used when you click 'Drives', in the apps menu..
And this fix package, I can't get to work at all. It always just halts at the part that says PETget package manager Updating menu, please wait... forever even after a clean install. I wind up doing a restart of X to get back to a working OS so I don't know if the update completed partly, at all, or completely.
Re: USB Thumb Drives
Right click on the bugfix pet file, convert to tgz, and extract the files to /rfxcasey wrote:And this fix package, I can't get to work at all. It always just halts at the part that says PETget package manager Updating menu, please wait... forever even after a clean install. I wind up doing a restart of X to get back to a working OS so I don't know if the update completed partly, at all, or completely.
This is basically the same as installing it.. Extracting each one individually, then restarting jwm or X after each, will be the safest way..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
OK thanks will give that a try but I have run into another "bug" of sorts.
I accidentally deleted the path for the xmame executable file in the xmame directories dialog and couldn't remember what path to enter. I figured I would boot from live cd and check the directory do I could enter it on the hard drive install.
Well I got an error message when trying to boot from live CD so I tried to boot from the HD and got the same error as follows while booting: Setting up the layered filesystem.... failed. Then there is a whole bunch more data. I searched around and found a related article http://www.murga-linux.com/puppy/viewtopic.php?t=36944 so this is apparently a puppy issue and not solely limited to Arcade. The fix it in the article but you may want to include this on future version of arcade just so it doesn't snag anyone else.
I accidentally deleted the path for the xmame executable file in the xmame directories dialog and couldn't remember what path to enter. I figured I would boot from live cd and check the directory do I could enter it on the hard drive install.
Well I got an error message when trying to boot from live CD so I tried to boot from the HD and got the same error as follows while booting: Setting up the layered filesystem.... failed. Then there is a whole bunch more data. I searched around and found a related article http://www.murga-linux.com/puppy/viewtopic.php?t=36944 so this is apparently a puppy issue and not solely limited to Arcade. The fix it in the article but you may want to include this on future version of arcade just so it doesn't snag anyone else.