PS3 sMAN 1.08n (by deank) - Adds new XMB Intergration Option, Improved ICON/SFO Scanning & more...

One of many legends in the PS3 Homebrew Community developer deank is back with a new progression of the sMAN plugin. We all know deank from projects like multiMAN, webMAN and now the sMAN plugin that has appeared to perhaps replaced (?) the original webMAN (aka webMAN Vanilla) project as now a new feature will allow you to choose between old style of "My Games" with the "XML" Mod, this option is off by default. As seen in the included pic in the release notes, the "XMB Intergration" can be toggled on/off easily in sMAN setup. The dev did not stop there with improving this PS3 Plugin in v1.08n additional details such as improved speed on scanning from external / internal hdd when extracting Game Icons / obtaining info from the PARAM.SFO can be seen with all details of this update​


sman_xmb1.jpg

  • sMAN 1.08n is available:


    sMAN version 1.08n Changes:
    • Added [x] XMB Integration option in setup for people who like the older xmb/xml style (off by default)
    • Improved scan speed from ntfs/internal hdd when extracting icons/sfo
    • sMAN resources in /dev_hdd0/tmp/wmtmp/res will not be overwritten if exist (at least until the next version)
    • Supports up to 2000 titles (even in XMB Integration mode)
    • Still uses the same amount of memory (~2300KB free while idle)


    Dean

    • Developer: @deank
    • Type of Release: A PS3 Plugin for use with Custom Firmware : Such as a COBRA CFW or other CFW types such as (STANDARD) with the ability to boot plugins via external applications ..
    • Short Description: the sMAN plugin takes deank original webMAN plugin and adds the new slaunch feature also developed by deank and merges them into a single plugin that also gives the ability with all the original webMAN features developed by deank.



  • History of Changes

    sMAN v1.07
    • It can be either 10 or 40 games per page. Both layouts can be switched with [R3].
    sMAN 1.06n
    • Some important parts of the plugin are rewritten and optimized to reduce stack usage
    • Returned another 112KB back to fg vsh :) (2316KB free - was 1920KB a month ago without ntfs :) so about 396KB less used)
    • Changed sman.bin to support longer game names/paths/icons - a rescan will be initiated
    • Cleaned some code (about 1000 lines gone after the optimization)
    • Loading games speed improved (at least the perceived speed)
    • sMAN will show the name of the loaded game as popup message (not the filename)
    • sMAN is now properly unloaded when requested (no zombie or dead threads should remain)
    • It supports up to 2000 titles (games/bd/dvd) now

    sMAN v1.05
    • Use [L2+R2] to start sMAN
    • The sprx is bigger (but actually uses less memory) because it contains some glued resources
    • It will use standard PS1/PS2/PSP/PS3/Blu-ray/DVD icons when there is no proper cover/image available
    • This version of the plugin must be named sman.sprx and loaded from (in this exact order):
      • /dev_hdd0/sman.sprx or
        /dev_hdd0/plugins/sman.sprx or
        /dev_flash/vsh/module/sman.sprx otherwise it won't work.​

    sMAN v1.02

    • Changed netiso/rawseciso implementation (external) - use plugin slot #0
    • Fixed crash when trying to load another PS1 title after one is played

    sMAN v1.01
    • Added "Setup" option in side-menu
    • Removed xml generation - no need for custom category_game.xml anymore
    • Removed xai_plugin/idle_plugin usage
    • Added x2 upscale for small images/covers (w/h < 336)
    • Added indication of current group mode (PS3 1 / xxx) under title name/path
    • Removed "My Games" entry from XMB - hold [START] to launch sMAN


Downloads:


Source: PSX-Place.com
 
Last edited:
Alright well I think i figured out the problem....kinda

The culprit seems to be the hdd. about 2 weeks ago I got a ps that i found had a 1tb seagate ssd in it! I've been using it just fine....so after I experienced this issue today, I re-installed rebug, rebuild database, restore ps3 system and did all that and the sman fatal error kept coming up.

so on a whim , I put back my older 750GB regular hdd which still had all my files in it and everything set up with rebug on 7.50...then i installed sMAN 1.09n and ....its working! smooth as butter!

so it seems that something is up in that hdd...where only webman vanilla works but wMM and sMAN don't! even after all the stuff I did above. so here with my old hdd, its all good again
To check if sman.sprx was corrupted during/after the transfer on the ssd, you could try to transfer it back from your ps3 to your pc and check its md5 sum.

You could also check S.M.A.R.T datas of the ssd to see its reliability.

In last resort, you could try to format your sdd drive via the recovery menu of the ps3. Just to be sure there was nothing that causes these issues on dev_hdd0 after all the changes/things you did on it.

Edit: nevermind, i think that bguerville is right :)
 
thanks @bguerville i tryed the original cmd ps3netsrv that come with wm1.47 but it's the same with little diffrent, the org ps3netsrv load less games than what the moded ps3netsrv.

and sorry @deank the new sman now dosen't freez my ps3 on
BEN 10 OMNIVERSE [BLUS31017].iso
BEN 10 OMNIVERSE 2 [BLUS31215].iso
but it freez after 5 and sometime 6 games after ben 10 games, so it's random but dose'nt go farther than this.

i test with org ps3netsrv it freez my ps3 in a deffrent game, and when i test with mod ps3netsrv it freez in another game, so it's kinda a random but the one fact is that i can't scan my games with out freezing my ps3.

thanks again guys
 
thanks @bguerville i tryed the original cmd ps3netsrv that come with wm1.47 but it's the same with little diffrent, the org ps3netsrv load less games than what the moded ps3netsrv.

and sorry @deank the new sman now dosen't freez my ps3 on
BEN 10 OMNIVERSE [BLUS31017].iso
BEN 10 OMNIVERSE 2 [BLUS31215].iso
but it freez after 5 and sometime 6 games after ben 10 games, so it's random but dose'nt go farther than this.

i test with org ps3netsrv it freez my ps3 in a deffrent game, and when i test with mod ps3netsrv it freez in another game, so it's kinda a random but the one fact is that i can't scan my games with out freezing my ps3.

thanks again guys
To help understand this potential issue, would you mind testing the original ps3netsrv with either multiman or webman 1.47 (not wMM) as well..?
 
Last edited:
To help understand this potential issue, would you mind testing the original ps3netsrv with either multiman or webman 1.47 (not wMM) as well..?
mmmm if i use wMM i don't have any problem with listing my games in XMB but sluanch show only 1000 game, so you can say i don't have any problem with wMM.

but i will test MM wM 1.47 and i will edit my post with the result

EDIT: i test MM with org ps3netsrv and everything is ok like wMM no problem.
 
Last edited:
How can I enable ftp server?
Failed to connect with error "ECONNREFUSED - Connection refused by server"
I'm using 1.10n
The ftp server is enabled by default. You don't need to enable it.
Did it use to work ok with sMan 1.09n or is this 1st time you try this ftp server?
Are you using using Rebug in dex mode?
 
The ftp server is enabled by default. You don't need to enable it.
Did it use to work ok with sMan 1.09n or is this 1st time you try this ftp server?
Are you using using Rebug in dex mode?

I'm using habib and not succeed to enable ftp server in all version of sMan
ftp server worked in Irisman
 
I'm using habib and not succeed to enable ftp server in all version of sMan
ftp server worked in Irisman
It does not work in any version of sMan? That is not normal at all. 1.09n worked very well. We need more details about your setup.
Does ftp work with webman or webMAN-MOD?
What about the rest of sMan? Is the GUI working? Does it mount games ok? Is everything working except the ftp server? If the rest of sMan is working can you try another ftp client?
 
Hi, I have the same problem, with sman 1.09 and 1.10 I do not connect Filezilla ftp, but in 1.08 I had no problem. The strange thing is that if I install WEBMAN if FTP works. Use Habib 4.81 snake 7.50 v2. If they could explain exactly how to configure the FTP would be appreciated.
 
No dramas with Filezilla on Windows here. Although I don't have an external hard drive connected at the moment.

I do have to manually refresh each folder as I enter it, as it seems to be falling back on old cached information or something and not showing the current contents in real-time. (example deleting wmtmp, restarting the ps3, refreshing sman, then connecting with filezilla shows no wmtmp folder upon entering /dev_hdd0/tmp/ until manually refreshing inside that directory)

I just connect via the quickconnect bar. ip address, ps3, ps3, 21.
I know it's bad practice, but I'm lazy and have the PS3 in DMZ to avoid any issues with UPnP / manual port forwarding depending on what I'm doing.

Capture.JPG


Quick connect:
Code:
Status:    Connecting to 192.168.1.100:21...
Status:    Connection established, waiting for welcome message...
Response:    220 sMAN ftpd 1.10n [NTFS:-2]
Command:    AUTH TLS
Response:    530 ERR
Command:    AUTH SSL
Response:    530 ERR
Status:    Insecure server, it does not support FTP over TLS.
Command:    USER ps3
Response:    331 OK
Command:    PASS ***
Response:    230 OK
Status:    Server does not support non-ASCII characters.
Status:    Logged in
Status:    Retrieving directory listing...
Command:    PWD
Response:    257 "/"
Status:    Directory listing of "/" successful

Manual refresh:
Code:
Status:    Retrieving directory listing of "/"...
Command:    TYPE I
Response:    200 TYPE OK
Command:    PASV
Response:    227 Entering Passive Mode (192,168,1,100,146,35)
Command:    MLSD
Response:    150 OK
Response:    226 OK
Status:    Directory listing of "/" successful
 
Last edited:
@Zoilus
I would not be surprised if the SSD was confirmed as the cause of your issues.. As a general rule most SSD are to be avoided. In my own experience, I noticed that SSD induce all sorts of strange behaviour cropping up over time. Some features work until they don't anymore for no obvious reasons.
After months of weird unexpected issues, I eventually had to switch back to a standard hdd although I was really enjoying things like file system checks in under 30s or very fast game data installation....

by avoid ...do you mean using them on the ps3? or as a general rule? lol
oh after after looking at it closely ...it turns out its an SSHD , so its a hybrid. I was wondering
why it would sometimes make noises like a regular hdd
 
by avoid ...do you mean using them on the ps3? or as a general rule? lol
oh after after looking at it closely ...it turns out its an SSHD , so its a hybrid. I was wondering
why it would sometimes make noises like a regular hdd
Yes SSD must be avoided as internal hdd replacement, they are ok in external usb enclosure though.
SSHD on the other hand should not be a problem...
Another thing to note is that new sata300 or sata600 drives can also be glitchy when they run at full transfer speed as the ps3 hdd controller only handles Sata150.
On certain drives you can reduce the SATA300/600 mode down to SATA150 by means of a jumper.

There is more information for you to read at the wiki. Check the section about Internal hdd in particular.
http://www.psdevwiki.com/ps3/Harddrive
 
The only successful ssd installation I have done on a ps3 was the ocz vertex 3 that had most of the "ssd features" built into the drive instead of relying on the controller. The rest of them always had weird issues. SSHD hybrid drive is ssd and hdd kind of glued together, essentially. So from the ps3 end it seems like a flash drive, but with more storage. I used to offer ssd as an option, but stopped quickly after the 3rd or 4th person had problems I couldn't explain, even on clean installs. :)
 
So weird because I experienced somewhat the opposite...

I had in total half a dozen different glitches when using a OCZ Vertex 3 in one of my slims. Even though, except one, all those glitches appeared over time...
I was never able to start the recovery menu.
After a couple of months Restoring file system would hang! Stuff of the kind...
On the other slim I used a OCZ Agility 4 for a few months. Again I was plagued by annoying glitches & freezes during specific operations.

Overall, from my experience, SSD seem to give very unpredictable results like you said...

I experienced no particular problems with my SSHD although I ended up replacing it with a standard hdd anyway. Only tested one SSHD though
 
Last edited:
Yeah I could see the lack of trim on the ps3 possibly being a problem long term with certain SSDs.

I'd guess that it depends how well the drive itself handles the delay from having to erase the blocks before being able to write to them, instead of them being automatically cleaned in advance. Might just end up queuing too many actions thinking it could handle them and getting overrun?

Sandforce controllers are just garbage in general in my experience.
 
@aldostools @Joonie

This change in stage2 storage_ext.c is wrong:

Code:
  cd_sector_size = (trackscount & 0xffff00)>>4; // <-- Use: trackscount = num_of_tracks | (cd_sector_size<<4);

All <<4 and >>4 must be <<8 and >>8 (shifting a byte and not octet). In its current implementation it breaks PS1 discs with more than 14 audio tracks and I don't think parses the sector size correctly at all.
 
Last edited:
@aldostools @Joonie

This change in stage2 storage_ext.c is wrong:

Code:
  cd_sector_size = (trackscount & 0xffff00)>>4; // <-- Use: trackscount = num_of_tracks | (cd_sector_size<<4);

All <<4 and >>4 must be <<8 and >>8 (shifting a byte and not octet). In its current implementation it breaks PS1 discs with more than 14 audio tracks and I don't think parses the sector size correctly at all.

The <<4 is ok because the valid cd sector sizes are:
2048 = 0x800
2336 = 0x920
2352 = 0x930
2448 = 0x990

As the last octet is always 0, I used <<4 instead of shifting a whole byte (<<8), to be able to use remaining 16 bits in the future if it is necessary.

Example for 32 tracks and sector size of 2352:
trackscount = num_of_tracks | (cd_sector_size<<4); <- passed to sys_storage_ext_mount_discfile_proxy
trackscount = 0x20 | (0x930<<4); = 0x20 | 0x9300 = 0x9320;

cd_sector_size = (trackscount & 0xffff00)>>4;
cd_sector_size = (0x9320 & 0xffff00)>>4; = (0x009300)>>4 = 0x00930 = 0x930 = 2352

Then we have trackscount &= 0xff;

trackscount &= 0xff; // supports up to 255 tracks
trackscount = trackscount & 0xff = 0x9320 & 0xff = 0x20 = 32;

As sMAN / wMM currently support up to 32 audio tracks, it is still in the range below 255.


EDIT:
If Joonie wish to add support for cd sector size 2368 (0x940), just need to change the 2 lines in storage_ext.c (lines 3229 & 3670):

if(cd_sector_size != 2352 && cd_sector_size != 2048 && cd_sector_size != 2336 && cd_sector_size != 2448) cd_sector_size = 2352;

to this:

if(cd_sector_size != 2368 && cd_sector_size != 2048 && cd_sector_size != 2336 && cd_sector_size != 2448) cd_sector_size = 2352;

Note: I replaced 2352 with 2368, instead of add another condition for 2368, because the condition cd_sector_size != 2352 is redundant.
 
@deank, sMAN is now working well for me. Thank you for all your hard work to make this plugin as awesome as it is. I have a quick question. I use custom .SFO files in wmtmp (so that the names have no special characters or do not appear in all caps), I use mulitple usb flash drives and I have noticed that when I change to a new one sMAN shows entries for both flash drives even though one is unplugged. Is this a result of using custom .SFO in wmtmp directory? Thank you.
 
guys does sman use files that use webman i see in my tmp folder files like slaunch.bin slist.bin does sman use this files? or this files only for slaunch (integrated with webman)
and what about xmb integration in sman? it changes game_category.xml?
Should I make a backup of game_category.xml and game_category_tool2.xml if im on rebug анд If I want to return to the webman?
and how to edit boot plugins
now it looks like this
/dev_hdd0/webftp_server_ps3mapi.sprx (i think this one old (remained after habib) )
/dev_hdd0/plugins/wm_vsh_menu.sprx
/dev_hdd0/plugins/slaunch.sprx

disable both slaunch and wm vsh menu?
or can i use vsh menu with sman?

sorry for noob questions)
 
Back
Top