pcsx2 won't load .gz zipped isos
#1
Hi, I just updated to 1.7.2117 of the nightly builds and now pcsx2 doesn't open my iso files. All my isos are compressed to .gz using 7zip. I didn't have this problem with 1.7.2116.

Here's my log after trying to run Burnout 3, it just boots straight to bios. Thanks in advance.

Code:
PCSX2 Nightly - v1.7.2117 Compiled on Dec 12 2021
Savestate version: 0x9a290000

Host Machine Init:
Operating System =  Microsoft Windows 10, 64-bit
Physical RAM    =  16305 MB
CPU name        =  Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz
Vendor/Model    =  GenuineIntel (stepping 05)
CPU speed        =  2.903 ghz (16 logical threads)
x86PType        =  Standard OEM
x86Flags        =  bfebfbff 7ffafbbf
x86EFlags        =  2c100000

x86 Features Detected:
SSE2.. SSE3.. SSSE3.. SSE4.1.. SSE4.2.. AVX.. AVX2.. FMA

The current power profile is 'Balanced'.
The current min / max processor states
AC: 5% / 100%
Battery: 5% / 100%

Reserving memory for recompilers...
HLE Host: Set 'host:' root path to: \

Patches: No CRC found, using 00000000 instead.
Error: iso-gzip read unsuccessful.
Path: [Unnamed or unknown]
ISO mounting failed: PCSX2 is unable to identify the ISO image type.
Kbd Accelerator 'F11' is mapped to unknown command 'Sys_FreezeGS'
Current Renderer: OpenGL
Created a OpenGL context
GL_VENDOR: NVIDIA Corporation
GL_RENDERER: NVIDIA GeForce RTX 2060/PCIe/SSE2
GL_VERSION: 4.6.0 NVIDIA 496.98
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
INFO: GL_ARB_sparse_texture is available
INFO: GL_ARB_sparse_texture2 is available
INFO: GL_ARB_gpu_shader5 is available
INFO: GL_ARB_shader_image_load_store is available
INFO: GL_ARB_clear_texture is available
INFO: GL_ARB_direct_state_access is available
INFO: GL_ARB_texture_barrier is available

Available VRAM/RAM:3840MB for textures
GS Lookup CRC:00000000
GS Lookup CRC:00000000
48000 SampleRate:
McdSlot 0 [File]: D:\PS2 Emulator & Games\pcsx2-v1.7.2117-windows-x86\memcards\Mcd001.ps2
McdSlot 1 [File]: D:\PS2 Emulator & Games\pcsx2-v1.7.2117-windows-x86\memcards\Mcd002.ps2
EE/iR5900-32 Recompiler Reset
BIOS rom1 module not found, skipping...
BIOS rom2 module not found, skipping...
BIOS erom module not found, skipping...
# Initialize memory (rev:3.63, ctm:196Mhz, cpuclk:147Mhz detected)
Frame buffer size set to  512x512 (3072x3072)
# Total accessable memory size: 32 MB (B:2:8:0) (363:2:7c30)
# TLB spad=0 kernel=1:12 default=13:30 extended=31:38
# Initialize Start.
# Initialize GS ...
# Initialize INTC ...
# Initialize TIMER ...
# Initialize DMAC ...
# Initialize VU1 ...
# Initialize VIF1 ...
# Initialize GIF ...
# Initialize VU0 ...
# Initialize VIF0 ...
# Initialize IPU ...
# Initialize FPU ...
# Initialize User Memory ...

PlayStation 2 ======== Hard reset boot
ROMGEN=2001-1004, IOP info (CPUID=1f, CACH_CONFIG=0, 2MB, IOP mode)
<20041105-175839,ROMconf,PS20200EC20041105.bin:11520>
# Initialize Scratch Pad ...
# Initialize Done.

EE DECI2 Manager version 0.06 Jul  4 2001 16:03:45
  CPUID=2e20, BoardID=0, ROMGEN=2001-1004, 32M

Patches: No CRC found, using 00000000 instead.
(IsoFS) Invalid partition descriptor encountered at block 0x10: ''


IOP Realtime Kernel Ver.0.9.1
    Copyright 1999 (C) Sony Computer Entertainment Inc.
Reboot service module.(99/11/10)
cdvd driver module version 0.1.1 (C)SCEI
Load File service.(99/11/05)
Multi Threaded Fileio module.(99/11/15)
iop heap service (99/11/03)
loadelf: fname rom0:OSDSYS secname all
loadelf version 3.30
Input ELF format filename = rom0:OSDSYS
0 00100000 0004c718 .....
Loaded, rom0:OSDSYS
start address 0x100008
gp address 00000000
# Restart Without Memory Clear.
# Initialize GS ...
# Initialize INTC ...
# Initialize TIMER ...
# Initialize DMAC ...
# Initialize VU1 ...
# Initialize VIF1 ...
# Initialize GIF ...
# Initialize VU0 ...
# Initialize VIF0 ...
# Initialize IPU ...
# Initialize FPU ...
# Initialize Scratch Pad ...
# Restart Without Memory Clear Done.
# Restart Without Memory Clear.
# Initialize GS ...
# Initialize INTC ...
# Initialize TIMER ...
# Initialize DMAC ...
# Initialize VU1 ...
# Initialize VIF1 ...
# Initialize GIF ...
# Initialize VU0 ...
# Initialize VIF0 ...
# Initialize IPU ...
# Initialize FPU ...
# Initialize Scratch Pad ...
# Restart Without Memory Clear Done.
Get Reboot Request From EE
ROM directory not found

PlayStation 2 ======== Update rebooting..
ROM directory not found

PlayStation 2 ======== Update reboot complete
cdvdman Init
rmreset start
rmreset end
clearspu: completed
Pad Driver for OSD (2000/12/05 18:05) 392, 128

IOP Realtime Kernel Ver.0.9.1
    Copyright 1999 (C) Sony Computer Entertainment Inc.
Reboot service module.(99/11/10)
cdvd driver module version 0.1.1 (C)SCEI
Load File service.(99/11/05)
Multi Threaded Fileio module.(99/11/15)
iop heap service (99/11/03)
read/write allocate memory 4000
open name rom0:ROMVER flag 1 data 48978
open fd = 2
loadmodule: fname rom0:ATAD args 0 arg
ATA: DEV9C version 0x0: unknown device detected
loadmodule: id 31, ret 1
loadmodule: fname rom0:HDDLOAD args 28 arg -osd
loadmodule: id -200, ret 1
open name rom0:FONTM flag 1 data 48978
open fd = 2
open name rom0:FNTIMAGE flag 1 data 48978
open fd = 2
open name rom0:SNDIMAGE flag 1 data 48978
open fd = 2
open name rom0:TEXIMAGE flag 1 data 48978
open fd = 2
open name rom0:ICOIMAGE flag 1 data 48978
open fd = 2
open name rom0:TZLIST flag 1 data 48978
open fd = 2
_spu_rev_offsetaddr 1f9021
### addr = 1034255  size = 28640
_spu_rev_offsetaddr 1d9021
### addr = 968719  size = 28640
open name rom0:ROMVER flag 1 data 48978
open fd = 2
open name rom1:DVDID flag 1 data 48978
open fd = -6
(UpdateVSyncRate) Mode Changed to DVD PAL.
Reply

Sponsored links

#2
yes it's no longer supported, there are better options available which we do support in CSO and CHD.
[Image: ref-sig-anim.gif]

Reply
#3
Ok, could you recommend an app that compresses to CSO or CHD? 7-zip doesn't do it and googling iso to cso gave me a bunch of apps that didn't work properly.
Reply
#4
chdman or maxcso.
both are command line tools
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
Reply
#5
I got chdman from the Mame website and watched a youtube video on how to use it, thanks a lot.
Reply
#6
How do I un GZ all my isos? I have used a program called Pigz for years to batch my entire collection into GZ but if they are now ruined because you took the feature out I will be pissed.
Reply
#7
(12-17-2021, 06:39 AM)Catlin Wrote: How do I un GZ all my isos? I have used a program called Pigz for years to batch my entire collection into GZ but if they are now ruined because you took the feature out I will be pissed.

tar will do it
unpigz will do it too

or just use latest pcsx2 dev build to use your gzipped isos again
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
Reply
#8
> yes it's no longer supported

It's supported. The latest downoad from https://github.com/PCSX2/pcsx2/releases/tag/v1.7.2137 can load gz ISOs.

I'm guessing the issue was this https://github.com/PCSX2/pcsx2/issues/5162 which was fixed shortly after it was reported, here https://github.com/PCSX2/pcsx2/commit/ab816543 .
Reply
#9
> It's supported. The latest downoad from https://github.com/PCSX2/pcsx2/releases/tag/v1.7.2137 can load gz ISOs.

It does load gz ISOs, but there seems to be some issue with the index file - it's not saved and/or not loaded correctly, so this results in (long-ish) indexing every time a gz ISO is loaded, or after pause/resume (and then used from memory apparently without saving it to disk).

I didn't bisect when the issue started, but it's not working fully as intended (index created once, then reused on every next time the gs ISO is accessed).
Reply
#10
> but there seems to be some issue with the index file

That's now fixed in v1.7.2138 ( https://github.com/PCSX2/pcsx2/commit/fa1b6493 ).

So there was one issue few days ago where gz ISO got broken completely.

That got fixed partially (index is loaded if it exists, but not saved if it's missing).

And today (just now) apparently fixed fully (index is saved if it's missing).

So gzipped ISO should now work normally like it always did.

One thing to note though - apparently the index file is not compatible between 32/64 versions of pcsx2. That is, if it's created with pcsx2 32, then only this version can load it later, and probably similar for pcsx2 64 - if it's created with this vpcsx2 version then only 64 can load it later.

So if switching between 32/64 version, then one of them can be configured to use a different name for the index file so that the 32 index file name would differ from the 64 index file name.

Either way, the index file can always be deleted and it will be created the next time the iso is loaded, compatible to the 32/64 version which created it.
Reply




Users browsing this thread: 1 Guest(s)