Hi there,
I have successfully been using ScummVm 1.0.0 on a 8GB USB Key.
I have now upgraded to a 320GB External USB Drive. This still utilises the USB Port on my SLIM PS2.
After transfering my ScummVm game files to the 320GB HD, all worked - while the drive was about 8GB full of data.
When the drive data, for example game backups for USBAdvance, exceeded 8GB, ScummVM stopped working and now hangs on the 0101 helix screen. So ScummVM 1.0.0 did work on my 320 GB HD but now it does not....
This does not affect the Damonfeuer 0.12 V3 version, it still works with the 320GB HD, but I cannot play Return To Zork, Discworld etc.
Is there any solution to this. Is there any code that states if HD size > 8GB then HDD else USB?
Thanks for any help you guys...
ScummVM 1.0.0 external USB HD stopped working
Moderator: ScummVM Team
Hi there Junebug,
...puzzling...
could you please confirm that the *.IRX you are using when running 0.12v3 and 1.0.0 are the same?
Have you tried copying 1.0.0 scummvm.elf binary over the 0.12v3 one and see if this makes a difference?
This guarantees you are running it from the same setup.
Please let us know.
Thanks!
-max
...puzzling...
could you please confirm that the *.IRX you are using when running 0.12v3 and 1.0.0 are the same?
Have you tried copying 1.0.0 scummvm.elf binary over the 0.12v3 one and see if this makes a difference?
This guarantees you are running it from the same setup.
Please let us know.
Thanks!
-max
Hi Max, thank you for replying to my problem.
Directory of G:\SCUMMVM1.0 (Where 1.0.0 is run from)
2009-11-12 00:56 10,421 CODYVDFS.IRX
2009-11-12 00:56 8,537 FILEXIO.IRX
2009-11-12 00:56 10,701 IOMANX.IRX
2009-11-12 00:56 3,413 POWEROFF.IRX
2009-11-12 00:56 11,745 PS2ATAD.IRX
2009-11-12 00:56 10,113 PS2DEV9.IRX
2009-11-12 00:56 54,549 PS2FS.IRX
2009-11-12 00:56 26,337 PS2HDD.IRX
2009-11-12 00:56 21,502 PS2HOST.IRX
2009-11-12 00:56 18,745 PS2MOUSE.IRX
2009-11-12 00:56 27,552 RPCKBD.IRX
2009-11-12 00:56 8,637 SJPCM.IRX
2009-11-12 00:56 26,421 USBD.IRX
2009-11-12 00:56 51,221 USB_MASS.IRX
2009-11-12 00:56 78,225 PS2IP.IRX
2009-11-12 00:56 13,077 PS2SMAP.IRX
Directory of G:\SCUMMVM (Where 0.12v3 is run from)
2009-04-17 15:54 10,421 CODYVDFS.IRX
2009-04-17 15:54 8,537 FILEXIO.IRX
2009-04-17 15:54 10,701 IOMANX.IRX
2009-04-17 15:54 3,413 POWEROFF.IRX
2009-04-17 15:54 11,745 PS2ATAD.IRX
2009-04-17 15:54 10,113 PS2DEV9.IRX
2009-04-17 15:54 54,549 PS2FS.IRX
2009-04-17 15:54 26,337 PS2HDD.IRX
2009-04-17 15:59 21,502 PS2HOST.IRX
2009-04-17 15:54 78,225 PS2IP.IRX
2009-04-17 15:54 18,745 PS2MOUSE.IRX
2009-04-17 15:59 13,077 PS2SMAP.IRX
2009-04-17 15:54 27,552 RPCKBD.IRX
2009-04-17 15:54 8,637 SJPCM.IRX
2009-04-17 15:54 26,421 USBD.IRX
2009-04-17 15:54 51,221 USB_MASS.IRX
Secondly I copied the 1.0.0 elf to the 0.12v3 folder and ran it using the older *.IRXs - it hung on the 0101 helix screen - as it does in the newer 1.0.0 folder.
It is puzzling as 1.0.0 has worked on the 320GB external USB HD, but only when less than approx. 8GB - could it be an issue with the Network code? Is there a version of 1.0.0 with no network code in? I know that the 0.12v3 elf has had this code removed (and works on SLIMS). Perhaps this is causing a confilct with SLIM PS2s when the USB HD size is > 8GB?
Or is there additional 'timeout' code, for USB HD access, which 0.12v3 did not use hence causing it to hang on 1.0.0?
Thanks for your support max. Any testing, let me know....
They are not the same - here are the directory listings:could you please confirm that the *.IRX you are using when running 0.12v3 and 1.0.0 are the same?
Directory of G:\SCUMMVM1.0 (Where 1.0.0 is run from)
2009-11-12 00:56 10,421 CODYVDFS.IRX
2009-11-12 00:56 8,537 FILEXIO.IRX
2009-11-12 00:56 10,701 IOMANX.IRX
2009-11-12 00:56 3,413 POWEROFF.IRX
2009-11-12 00:56 11,745 PS2ATAD.IRX
2009-11-12 00:56 10,113 PS2DEV9.IRX
2009-11-12 00:56 54,549 PS2FS.IRX
2009-11-12 00:56 26,337 PS2HDD.IRX
2009-11-12 00:56 21,502 PS2HOST.IRX
2009-11-12 00:56 18,745 PS2MOUSE.IRX
2009-11-12 00:56 27,552 RPCKBD.IRX
2009-11-12 00:56 8,637 SJPCM.IRX
2009-11-12 00:56 26,421 USBD.IRX
2009-11-12 00:56 51,221 USB_MASS.IRX
2009-11-12 00:56 78,225 PS2IP.IRX
2009-11-12 00:56 13,077 PS2SMAP.IRX
Directory of G:\SCUMMVM (Where 0.12v3 is run from)
2009-04-17 15:54 10,421 CODYVDFS.IRX
2009-04-17 15:54 8,537 FILEXIO.IRX
2009-04-17 15:54 10,701 IOMANX.IRX
2009-04-17 15:54 3,413 POWEROFF.IRX
2009-04-17 15:54 11,745 PS2ATAD.IRX
2009-04-17 15:54 10,113 PS2DEV9.IRX
2009-04-17 15:54 54,549 PS2FS.IRX
2009-04-17 15:54 26,337 PS2HDD.IRX
2009-04-17 15:59 21,502 PS2HOST.IRX
2009-04-17 15:54 78,225 PS2IP.IRX
2009-04-17 15:54 18,745 PS2MOUSE.IRX
2009-04-17 15:59 13,077 PS2SMAP.IRX
2009-04-17 15:54 27,552 RPCKBD.IRX
2009-04-17 15:54 8,637 SJPCM.IRX
2009-04-17 15:54 26,421 USBD.IRX
2009-04-17 15:54 51,221 USB_MASS.IRX
Yes I did - First I copied the 0.12v3 elf into the 1.0.0 folder and it ran successfully - using the lastest *.IRXs.Have you tried copying 1.0.0 scummvm.elf binary over the 0.12v3 one and see if this makes a difference?
Secondly I copied the 1.0.0 elf to the 0.12v3 folder and ran it using the older *.IRXs - it hung on the 0101 helix screen - as it does in the newer 1.0.0 folder.
It is puzzling as 1.0.0 has worked on the 320GB external USB HD, but only when less than approx. 8GB - could it be an issue with the Network code? Is there a version of 1.0.0 with no network code in? I know that the 0.12v3 elf has had this code removed (and works on SLIMS). Perhaps this is causing a confilct with SLIM PS2s when the USB HD size is > 8GB?
Or is there additional 'timeout' code, for USB HD access, which 0.12v3 did not use hence causing it to hang on 1.0.0?
Thanks for your support max. Any testing, let me know....
Hi there Junebug!
Here I come to the rescue ;=)
I assume that your version of 0.12v3 is the one with net/hd disabled.
So I uploaded 2 release candidates for ScummVM PS2 1.1.0 for you:
- http://www.sendspace.com/pro/dl/rgiyak
(with net & hd)
- http://www.sendspace.com/pro/dl/uxfuwi
(without net & hd)
I believe the second one should work for you for the best ScummVM experience ever
Please let me know.
>> Thanks for your support max. Any testing, let me know....
Well, if you want to test Groovie and Draci which I still
had not a chance to test, that might come handy
Any regression report too.
Thanks!
-max
Here I come to the rescue ;=)
I assume that your version of 0.12v3 is the one with net/hd disabled.
So I uploaded 2 release candidates for ScummVM PS2 1.1.0 for you:
- http://www.sendspace.com/pro/dl/rgiyak
(with net & hd)
- http://www.sendspace.com/pro/dl/uxfuwi
(without net & hd)
I believe the second one should work for you for the best ScummVM experience ever
Please let me know.
>> Thanks for your support max. Any testing, let me know....
Well, if you want to test Groovie and Draci which I still
had not a chance to test, that might come handy
Any regression report too.
Thanks!
-max
Hi Max,
Thank you for helping me try and find a solution to my problem.
I have tested SCUMMVM-1.1.0n.ELF and SCUMMVM-1.1.0.ELF on both an 8GB USB key and a 320GB USB HD on my SLIM PS2.
My Results
==========
(1) 8GB Key
SCUMMVM-1.1.0n.ELF - works fine, no problems
SCUMMVM-1.1.0.ELF - works fine, no problems
SVM12V2_SLIM_T3.ELF (0.12v3) - works fine, no problems
(2) 320 GB USB HD
SCUMMVM-1.1.0n.ELF - Hangs on 0101 helix screen after 2 seconds
SCUMMVM-1.1.0.ELF - Hangs on 0101 helix screen after 15 seconds
SVM12V2_SLIM_T3.ELF (0.12v3) - works fine, no problems
From this I conclude that SCUMMVM-1.1.0n.ELF (without HD/Network) attempts to get to the main menu screen quicker than then the SCUMMVM-1.1.0.ELF version - this is as it does not need to check for a network connection I imagine, which is what we want.
But unfortunately both SCUMMVM-1.1.0*.ELF versions still hang at the 0101 Helix screen on my SLIM PS2 with 320GB USB HD.
There must be something else in the SCUMMVM-1* code which is causing it to hang when using the USB HD, which is not there in the SVM12V2_SLIM_T3 code?
Is there a timing issue or a USB size issue when running SCUMMVM-1* immediately before the main menu appears, i.e. when the 0101 helix is spinning?
Is the 0101 screen waiting for something, or checking something? This may cause the hanging.
Thanks again for helping me Max - is there anything else I can try to get it to work?
Thank you for helping me try and find a solution to my problem.
I have tested SCUMMVM-1.1.0n.ELF and SCUMMVM-1.1.0.ELF on both an 8GB USB key and a 320GB USB HD on my SLIM PS2.
My Results
==========
(1) 8GB Key
SCUMMVM-1.1.0n.ELF - works fine, no problems
SCUMMVM-1.1.0.ELF - works fine, no problems
SVM12V2_SLIM_T3.ELF (0.12v3) - works fine, no problems
(2) 320 GB USB HD
SCUMMVM-1.1.0n.ELF - Hangs on 0101 helix screen after 2 seconds
SCUMMVM-1.1.0.ELF - Hangs on 0101 helix screen after 15 seconds
SVM12V2_SLIM_T3.ELF (0.12v3) - works fine, no problems
From this I conclude that SCUMMVM-1.1.0n.ELF (without HD/Network) attempts to get to the main menu screen quicker than then the SCUMMVM-1.1.0.ELF version - this is as it does not need to check for a network connection I imagine, which is what we want.
But unfortunately both SCUMMVM-1.1.0*.ELF versions still hang at the 0101 Helix screen on my SLIM PS2 with 320GB USB HD.
There must be something else in the SCUMMVM-1* code which is causing it to hang when using the USB HD, which is not there in the SVM12V2_SLIM_T3 code?
Is there a timing issue or a USB size issue when running SCUMMVM-1* immediately before the main menu appears, i.e. when the 0101 helix is spinning?
Is the 0101 screen waiting for something, or checking something? This may cause the hanging.
Thanks again for helping me Max - is there anything else I can try to get it to work?
Hi Junebug,
>> My Results
thanks for your feedback!
>> From this I conclude that SCUMMVM-1.1.0n.ELF (without
>> HD/Network) attempts to get to the main menu screen
>> quicker than then the SCUMMVM-1.1.0.ELF version -
>> this is as it does not need to check for a network
>> connection I imagine, which is what we want.
Actually network handshaking is not performed until later
(when you browse for games, etc.). It's likely because it
is loading more drivers and trying to detect the network
adapter and hd, and timeouts (after a few secs) when it
fails, that's why it takes longer.
>> Is the 0101 screen waiting for something, or checking
>> something? This may cause the hanging.
Alas, many things:
- loading the drivers
- boostrapping the hw
- loading the .ini
- loading the themes
- etc. etc.
It might fail in more than one place...
If you have a chance to execute scummvm from remote
(ps2link plus ps2client) you will be able to detect
at what stages it fails by reading the debug output
on your console.
Unluckily all my ScummVM/PS2 time is going into
preparing the 1.1.0 release and I'm not able to
reproduce your PS2 behaviour here, so it's kind
of a guessing game.
Couple of ideas:
a) what happens is you plug both the USB key (and
boot ScummVM from there) and the USB HD?
b) have you tried leaving the PS2 on for a few minutes
after the "helix has hanged"? Try 5 to 30 minutes
depending on how many files you have on USB HD
c) as a temporary fallback (but it might take a looooong
time before we are able to trace your regression since
we have a few items TODO: dynamic plugins, file handle
cache, 16 bpp, etc.) you could try to plug the hd on
your PC / laptop (make sure they are in the 192.168.0.x
range - your PS2 will be 192.168.0.10) and try to ping
your PS2. If it works, execute "ps2client listen" from
the place where your USB HD is mounted (I'm assuming u
use Linux) and you will able to access all the ScummVM
games there.
The beauty of this solution is that you can keep all your
ScummVM games in a single place, so you can play the same
game on your PC, laptop and PS2 and share the saved games
I won't be able to followup with the forum for a few days,
but please let me have your feedback.
Thanks!
-max
>> My Results
thanks for your feedback!
>> From this I conclude that SCUMMVM-1.1.0n.ELF (without
>> HD/Network) attempts to get to the main menu screen
>> quicker than then the SCUMMVM-1.1.0.ELF version -
>> this is as it does not need to check for a network
>> connection I imagine, which is what we want.
Actually network handshaking is not performed until later
(when you browse for games, etc.). It's likely because it
is loading more drivers and trying to detect the network
adapter and hd, and timeouts (after a few secs) when it
fails, that's why it takes longer.
>> Is the 0101 screen waiting for something, or checking
>> something? This may cause the hanging.
Alas, many things:
- loading the drivers
- boostrapping the hw
- loading the .ini
- loading the themes
- etc. etc.
It might fail in more than one place...
If you have a chance to execute scummvm from remote
(ps2link plus ps2client) you will be able to detect
at what stages it fails by reading the debug output
on your console.
Unluckily all my ScummVM/PS2 time is going into
preparing the 1.1.0 release and I'm not able to
reproduce your PS2 behaviour here, so it's kind
of a guessing game.
Couple of ideas:
a) what happens is you plug both the USB key (and
boot ScummVM from there) and the USB HD?
b) have you tried leaving the PS2 on for a few minutes
after the "helix has hanged"? Try 5 to 30 minutes
depending on how many files you have on USB HD
c) as a temporary fallback (but it might take a looooong
time before we are able to trace your regression since
we have a few items TODO: dynamic plugins, file handle
cache, 16 bpp, etc.) you could try to plug the hd on
your PC / laptop (make sure they are in the 192.168.0.x
range - your PS2 will be 192.168.0.10) and try to ping
your PS2. If it works, execute "ps2client listen" from
the place where your USB HD is mounted (I'm assuming u
use Linux) and you will able to access all the ScummVM
games there.
The beauty of this solution is that you can keep all your
ScummVM games in a single place, so you can play the same
game on your PC, laptop and PS2 and share the saved games
I won't be able to followup with the forum for a few days,
but please let me have your feedback.
Thanks!
-max
Hi sunmax, thanks for your ideas and suggestions, I can imagine how busy it is to maintain the ScummVM port to PS2 - but we should all thank you for maintaining this great software on our PS2s - I can only hope than we can enjoy Myst and Riven sometime in the future 
Regarding my issue, I am unsure if ULaunchELF will recognise 2 mass: devices, I have only every run it with 1 mass: device.
I do think your suggestion about hanging on the 0101 helix screen due to scanning the root directory may be valid. When I first used 1.0.0 everything was fine, when I added about 5 game backups for USBAdvance, those files resided in the root of mass: and 1.0.0 still worked - as I added more game backups - (about 15) 1.0.0 started to hang on the 0101 screen. Perhaps the ScummVM code tries to iterate the files, or perhaps tries to establish the size of files and has a buffer over run, or the datatype used for storing the file array/size is too small when there is GBs of data in mass: root causing it to hang??
I don't knpw if there is code in ScummVM which expects it to run from a CD/DVD and when the root size is over, say 5.5GB, it hangs?? As it is over the size of a DVD?
Regarding my issue, I am unsure if ULaunchELF will recognise 2 mass: devices, I have only every run it with 1 mass: device.
I do think your suggestion about hanging on the 0101 helix screen due to scanning the root directory may be valid. When I first used 1.0.0 everything was fine, when I added about 5 game backups for USBAdvance, those files resided in the root of mass: and 1.0.0 still worked - as I added more game backups - (about 15) 1.0.0 started to hang on the 0101 screen. Perhaps the ScummVM code tries to iterate the files, or perhaps tries to establish the size of files and has a buffer over run, or the datatype used for storing the file array/size is too small when there is GBs of data in mass: root causing it to hang??
I don't knpw if there is code in ScummVM which expects it to run from a CD/DVD and when the root size is over, say 5.5GB, it hangs?? As it is over the size of a DVD?