Can't install on Win 7 64 Bit

[dulciepercy]

Hi

Tried installing Mu.lab 3 under Win 7 64 bit Home Premium.

The transport panel, recording panel, and all the racks have no text or buttons, and don't respond to my clicks.

Can anyone help. If it helps I'll upload an image somewhere.

Thanks
Dulcie

[/img]

[pljones]

I don't think Home Premium 64-bit has full support for running 32-bit applications. You need Professional or Ultimate for that.

[MuTools]

The fact that dulciepercy sees the Transport Panel etc means Windows has launched the application, imho, so i think it's more an issue with the unzipping.

Not sure how you unzipped the zip package but it should result in this folder structure (i'm emphasizing the graphics folders):

Code: Select all

+ mulab-win
  + MULAB
    + App
      + Audio
      + Graphics
        + LooxPhat
          + Common
            + Fonts
            + Formats
            + ...
          + MultiSampla
          + MuSynth
          + ...
      + Library
    + User

I it like that?

Eventually try a fresh re-install.

[Improviser]

I don't think Home Premium 64-bit has full support for running 32-bit applications. You need Professional or Ultimate for that.

In addition to Windows XP, I have run Win 7 64-bit Home Premium (since its launch date), and never had the sort of problem that dulciepercy mentions - and that was with MU.LAB 2.7, and all M3-Test versions, and MU.LAB 3.

So, from here, it looks less likely to be due to the 64-bit system ?

Also (something I keeping meaning to ask Jo about), am I right in thinking that the creation of the Mulab folder and its contents (when unzipping the download), doesn't cause changes in the Windows registry ?

Les J.

[Nielzie]

I'm using Mu.lab 3 under Win 7 64 bit Home Premium too. It runs without any problems.

The fault you are probably making is that you "installed" (extracted/copied as there is unfortunately no real installer for Windows) it into the "Program Files" directory (like you were probably used to in an 32-bit environment). That directory is now only for 64-bit applications. Since Mu.Lab 3 is a 32-bit application it should be installed into the "Program Files (x86)" directory.

[wrench45us]

there's all sorts of parallelisms for running 32 bit (x86) applications on an x64 system

and it's confusing because many folders (including Program Files and system32) that were once for 32 bit are now re-assigned for x64 -- never mind the parallel registry structure where 32 bit objects will be registered in wow64

[Improviser]

I'm using Mu.lab 3 under Win 7 64 bit Home Premium too. It runs without any problems.

The fault you are probably making is that you "installed" (extracted/copied as there is unfortunately no real installer for Windows) it into the "Program Files" directory (like you were probably used to in an 32-bit environment). That directory is now only for 64-bit applications. Since Mu.Lab 3 is a 32-bit application it should be installed into the "Program Files (x86)" directory.

Here, on Win 7 64-bit, I normally have the MULAB folder installed in a location such as : "C:\Mutools", or "C\Mutools\mulab-3-0-38-win", rather than in "C\Prpgram Files (x86)".

But, just for interest, I copied and pasted the Mulab folder (and contents) into the "Program Files (x86)" folder, where it worked ok - but then I moved it into the "Program Files" folder ('reserved for 64-bit'), and as far as I can tell, it works fine in that location too - and indeed anywhere else I may care to put it.

I just mention this as an observation, as I'm not knowledgeable about the technicalities of 32-bit v. 64-bit.

Les J.

[multree]

try disabling the UAC and reinstall

[pljones]

I've got UAC on and it's fine here.

[cytone]

As an aside if you put MU.LAB in the Windows 7 program files (x86) directory you will have to deal with Virtual Store which is a p.i.t.a.
Best in my opinion to use any other directory.

[pljones]

Works flawlessly in PF(86) here.

[MuTools]

Based on what dulciepercy wrote, MU.LAB runs fine, but some graphic files are not located properly, for some reason. That's why i think it's just something with the unzipping.

[dulciepercy]

Thanks for all the replies. The answer turned out to be the extraction one - it hadn't unzipped correctly, which was a problem with not understanding file handling in Win7. Anyway we are away so thanks

Dulcie

[MuTools]

Glad it's solved