Potential issue with Win7 x86 and our 64-bit detection stuff

Questions and bug reports for Beta releases should be posted here.
Forum rules
Help us help you:
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
User avatar
inpheaux
Administrator
Administrator
Posts: 563
Joined: January 16th, 2008, 9:14 pm

Potential issue with Win7 x86 and our 64-bit detection stuff

Post by inpheaux »

DagothUrReturns, over on SA wrote:Hmm, had this issue with my first post upgrade download:

» Unpacking failed, [Error 216] This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher

Running 32bit Win7 on an Intel proc and I've installed the 32bit version of SAB.
Looks like we either failed to run the right unrar binary, or the "right" binary isn't actually right.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Potential issue with Win7 x86 and our 64-bit detection stuff

Post by shypike »

Very strange.
I run it on 32bit WHS, 32bit XP and 64bit Win7. Nobody of the release testers ran it on Win7-32bit?
Could be one of these nasty "required DLL's" again,  but unrar should not require any.

Could you ask him whether he has a folder called c:\windows\SysWow64 ?
That one should appear only on Vista/Win7 64bit.
Unless I am very mistaken it should not exist on a 32bit system.

Edit: I'll change the 64bit detection in Beta2.
Either look in the registry or check the value of the environment variable "processor_architecture".
It's "AMD64" for a 64-bit OS (weird, but there are historical reasons for this).
That's the official way of detecting it, don't know why I didn't think of that before.
Last edited by shypike on November 26th, 2009, 7:04 am, edited 1 time in total.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Potential issue with Win7 x86 and our 64-bit detection stuff

Post by shypike »

Just tested on a maiden Win7-32bit (VMWared) with Beta1.
Runs fine, no par2 or unrar problems.
dur
Newbie
Newbie
Posts: 2
Joined: November 26th, 2009, 11:18 pm

Re: Potential issue with Win7 x86 and our 64-bit detection stuff

Post by dur »

Hey, I'm DagothUrReturns from SA; inpheaux just approved my account for me.

I do have the SysWOW64 directory in my windows directory, but according to my system properties screen and the architecture environment variable i'm running 32bit (x86). I don't really know what to make of that.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Potential issue with Win7 x86 and our 64-bit detection stuff

Post by shypike »

Supposing the SysWOW64 folder is empty, just remove it.
It should not be there.

We will change the detection method to a safer one.

In the mean time you could replace the 64bit programs with 32bit ones.
Just look in the SABnzbd\win folder.
dur
Newbie
Newbie
Posts: 2
Joined: November 26th, 2009, 11:18 pm

Re: Potential issue with Win7 x86 and our 64-bit detection stuff

Post by dur »

SysWOW64 has a bunch of stuff in it so I'll leave it be. I'll stick some 32bit executables into the SAB folder like you said. Thanks for the help.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Potential issue with Win7 x86 and our 64-bit detection stuff

Post by shypike »

OK, next release will have this fixed.
Post Reply