New blog post up:

FPSE – Playstation emulator and BSzili’s multibutton pad plugin

https://morphosuser.wordpress.com/2015/10/28/fpse-playstation-emulator-and-bszilis-multibutton-pad-plugin/

Quote:

Nice Review/Tutorial!

Which ISO did you downloaded for Adventures of Lomax? I 've tried running it but without any success (I used the one from isozone). If you burn a game, insert it on dvd/cd-rom and you have it connected with audio cable to a SB Live, will the CDDA music work? Btw, GT2 which didn't worked in previous FPSE version, now works for me. Nice blog update :)

I have not tried to burn any games. The idea didn't occur to me. I might have to try it

There are many different sites to try. I don't remember which version works but one of them will

The REDUMP series at The Iso Zone works often.

So if I understand well, it is now possible to use all buttons ?

Made some minor corrections: https://morphosuser.wordpress.com/2015/10/28/fpse-playstation-emulator-and-bszilis-multibutton-pad-plugin/

@Simon

Yes, that is correct

I have tried it, but pad direction don't work for me, i use a logitech precision gamepad

[ Edited by acepeg 31.10.2015 - 00:21 ]

The only pas I know work for sure is the XBox 360 controller (with a cord).

Sensors.library supports generic HID gamepads, not just the XBox360 controller. If you have one which doesn't work with the plugin, contact me via mail or PM.

PS4 gamepad doesn't work with the plugin. Is there a way to make it works?

This method is worth trying.

New blog post up:

Wings Remastered Demo

https://morphosuser.wordpress.com/2015/11/06/wing-remastered-demo/

A Nice read! Thanks!

New blog post up:

Connecting MorphOS to a network

https://morphosuser.wordpress.com/2015/11/16/connecting-morphos-to-a-network/

Quote:
very, very helpful. thank you for the post!

-- eliyahu

Quote:

Thanks!
Very helpfull and nice guide! :)

Quote:

Few notes...

First, your MorphOS is already connected to a network when you can access the internet, but it's more about connecting to a network share (or more precisely mounting a SMB or Samba share). SMB is a Windows file sharing protocol and Samba is a free re-implementation of that for other systems.

So SMBFS means SMB (or SaMBa) File System, and it mounts a shared remote directory on the filesystem level to your MorphOS system. It's just a lightweight client program and you can't share anything from your MorphOS with it. To share some files from MorphOS you'd need a full installation of Samba (to get the server components), but it's much more bloated, so if you can live with just mounting other shares I wouldn't recommend to install it.

And then to the more important stuff :)

When you add your own mounting lines and also make the quit scrpt, you don't actually need the "Smart_SMBFS" at all, unless you just want to pick the icons or something from it. But the actual Smart_SMBFS script is totally useless for you. The rest of the lines you leave there are just for dismounting a single share (in a clumsy way) if you run the script again. And it won't even work in this case.

So, you could very well just create two totally new scripts with your lines on it.

Or if you want to take the toggling of mounting/dismounting with the one and same script, then it could look like this for example:

IF NOT EXISTS env:smbrem
RUN >NIL: smbfs //mediacenter/douga workgroup foo volume Douga devicename smb0
RUN >NIL: smbfs //mediacenter/momo workgroup foo volume Momo devicename smb1
RUN >NIL: smbfs //yasupc/download workgroup foo volume A1_Download devicename smb2 username Yasu password xxx
RUN >NIL: smbfs //yasupc/video workgroup foo volume A1_Video devicename smb3 username Yasu password xxx
RUN >NIL: smbfs //yasupc/shared workgroup foo volume A1_Shared devicename smb4 username Yasu password xxx
SetEnv smbrem 1
ELSE
RUN >NIL: break `status com “smbfs ‘//mediacenter/douga'”`
RUN >NIL: break `status com “smbfs ‘//mediacenter/momo'”`
RUN >NIL: break `status com “smbfs ‘//yasupc/download'”`
RUN >NIL: break `status com “smbfs ‘//yasupc/video'”`
RUN >NIL: break `status com “smbfs ‘//yasupc/shared'”`
Unsetenv smbrem
ENDIF

BTW. you can also dismount SMBFS shares one by one from the Eject screenbar module on the MorphOS with your mouse.


[ Edited by jPV 17.11.2015 - 10:39 ]

@jPV

You are right of course. I guess it's my age as for me "network" has always been about connecting computers with each other.

Well, having a "Share" drawer solved the problem for me. Even though I know it's not enough for some people.

I will try your script. It looks like a better option. In my defence I know nothing about these things and this solution worked great for me. So great I wanted to share it. After all, my blog is geared towards beginners like myself

Nice guide, thanks. BTW: why can MOS not go online automatically when the cable is plugged in after booting? The computer must be rebooted once more to make it work. I tried to run the network startup script after I plugged in the cable after the reboot but it did nothing.

@connor

I have no idea. Both network and internet works fine here. Does anyone else have a clue?

[ Edited by Yasu 17.11.2015 - 19:48 ]

Quote:
As a workaround, you can type the following command once the cable is plugged in:
Run >NIL: NetConfig autoconfig

And you should be online...
For easy access, I have this in a menu created using CRABUM.

Thanks for the hint, I will try it next time. Can the link be set up automatically when the cable is put in? How is it handled with WLAN btw?

I'm a network noob and I don't get it: I have a NAS here (Fritzbox inbuild NAS). It's name is NASbox. I can ping the NASbox by name and access it by ftp from MorphOS. Fine so far
But this doesn't work:

smbfs //NASbox/ workgroup NASbox volume NAS devicename smb0 username zylesea password ******
yields a
smbfs: ERRDOS - ERRnosuchshare (Share name not found).
smbfs: Cannot connect to server (5, Input/output error).
smbfs: Could not connect to server (5, Input/output error).

Anyone an idea? Replacing NASbox with the IP address doesn't change it. Aceess from Win works flawless.

smbfs //NASbox workgroup NASbox volume NAS devicename smb0 username zylesea password ******
yields a
smbfs: Invalid share name 'NASbox'.

@ Zylesea

Have you considered that this might be a case sensitivity issue? Have you tried entering all names with lower cases? Also, have you tried "smbfs /nasbox/nas workgroup ..."?

Quote:

Yeah, but you could very well comment out all of the other lines in Smart_SMBFS script but your own lines. I don't know if it's good to confuse beginners with lines which don't work and are useless. I think they never learn what's going there because they now don't understand why you have those extra commands there and it just seems more complicated than it is :)