Installing Arch64 via 32-bit vm

Hi!
I want to install Arch64 on my HD via VirtualBox (as described here: https://wiki.archlinux.org/index.php/In … VirtualBox ). My processor apparently does not support 64-bit virtualization, i.e. the virtual machine will run at 32-bit. Is this a problem for installing the 64-bit version on the HD though?
Last edited by fweth (2012-11-16 23:21:27)

Sorry, I think I expressed myself ambiguously. The host is 64-bit, but apparently it does not support 64-bit virtualization ('Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.') So I ask if I can download the Arch installer (which is dual architecture in the current version), run it in the 32-bit vm and install Arch64 on the HD (which I will continue to use with my 64-bit machine). But if you say that qemu can virtualize a 64-bit system on any host, this might be another alternative, thanks.
Last edited by fweth (2012-11-21 01:10:31)

Similar Messages

How to cross compile 32bit packages on Arch64 via distcc?

Is there a way to cross compile 32 bit packages on Arch64 via distcc?
Use 32bit chroot on Arch64, maybe?
If anyone has done such things, please tell me how.
Thank you very much!

Themaister wrote:http://wiki.archlinux.org/index.php/Arc … bit_system <--- good place to start
That's exactly what I followed to make a 32bit chroot on a 64bit machine. Then just use pacman inside the chroot to install the base-devel group, and you can start compiling packages from AUR, exactly the same way as you usually do. That's what I do (I have eee laptop on which it's pain to compile, so I use my 64bit machine for compiling). Then just transfer the newly created packages to the 32bit machine and install...
I don't use distcc for that, so can't help you with this, sorry.

Tutorial: Installing Windows XP 64-bit

After the fairly crappy time I had installing the 64 bit version of Win XP on my computer and peicing together various bits of information contained in various threads on this board in order to make it work, I've decided that I'm going to attempt to write as complete a tutorial as possible detailing the install process from beginning to end in hopes that it helps prevent people from running into the same problems I did. Anyways:
Step 1 - Acquire a copy of Windows XP 64-bit
Obviously you need a copy before you can install it, and you can get a free beta copy of Windows XP 64-bit Edition from here:
http://www.microsoft.com/windowsxp/64bit/downloads/upgrade.asp
You can either download the file (it's about 450 MB, though if you're on broadband your transfer will be over fairly quickly...microsoft.com servers always seem to offer excellent download speeds), or have physical CD's shipped to you. Either way it doesn't cost anything, all you have to do is fill out their form, and they'll give you your stuff.
Step 1a - Burn the .iso file to a CD
This section is probably wholly unnecessary, but for the sake of completeness, I'll include it...
If you had microsoft ship you a premade CD, skip this step. However, if you downloaded your copy of Win XP 64, you'll need to burn the image file you downloaded to a CD before you can use it. To do this, open your preferred burning software (I'd recommend using Nero), and select "Burn Image" (or the equivalent option for your software), and specify the .iso file you downloaded as the image file to burn. You should have your CD in a matter of minutes.
Make certain that you note and record the CD-key contained in the e-mail microsoft sent you. Writing this on the CD would be a good idea, as would printing out a copy of the e-mail.
NOTE: Do not burn the ISO file itself to a CD (i.e. create a new data CD and just drag the ISO file into the compilation window)...this will not work as it will put the file itself onto the disc, rather than the CD image contained within the ISO, which is what you want.
Step 2 - Prepare your system
Carefully preparing things before you attempt to install Windows XP 64 can save you a lot of headaches when install time actually comes.
First of all you want to make sure you have a seperate drive/partition to install Windows XP 64 onto (unless you're crazy enough to want a beta operating system to be your full-time OS...and I've seen Win XP 64 in action, and trust me, you do not want this just yet). If you are using RAID make sure you are using the VIA controller and not the Promise controller as from what I've heard there are no 64-bit drivers out yet for the Promise RAID controller. Also if you are using RAID, be sure to read the following thread, which details the process of putting the 64-bit RAID drivers onto a floppy disk, and follow the instructions carefully:
https://forum-en.msi.com/index.php?threadid=40859&sid=
Next, download all applicable drivers you can and save them in a sensible place (like c:\win64drivers). If the driver comes in an archive, be sure to pre-extract it as well (Win XP 64 does not come with native zip/rar support). It's okay if you don't want to get/cannot find all the drivers you'll need for your system, but at the very least make sure you download and extract the 64-bit ethernet adapter driver appropriate to your setup (most likely the RealTek RTL8169/8110 drivers), otherwise you'll be without internet (which makes downloading additional driver and program files kind of difficult). You may also want to pre-download the installation files for some of the more essential program, like Winzip and WinRAR. The best place I found to find 64-bit drivers is located here:
http://www.planetamd64.com/modules/mx_pafiledb/dload.php?sid=
Step 3 - Configure your BIOS
Certain BIOS settings can screw up the install process, causing it to lock up at certain points, so it's worth taking the time to make sure things are set properly.
Anyways, reboot your computer and go to the BIOS setup area, and make sure that "USB Legacy Support" is disabled, and that "Cool'n'Quiet" support is enabled...this will help reduce the chances of your installer hanging. I found that after my install had completed I was able to re-enable USB Legacy support and have everything still work fine, but your results may vary, and different BIOS versions may have different effects on the installer. I installed with BIOS version 1.20.
While you're here, check your Boot Order settings and make sure that your CD/DVD drive is listed before your HDD is, and then insert your Windows XP 64 CD into the drive. Save your settings and exit.
Step 4 - Installing Windows XP 64
When the computer reboots from step 3, you should see a message that says "Press any key to boot from CD..," so locate the "any" key and press it, and the windows installer will load.
If you've done everything mentioned in the above steps, your install process should hopefully be a painless one, free of the errors and random stupid crap that caused me to spend several hours doing something that shouldn't have taken more than 30 minutes. Select your desired install path (being careful to make sure that you're not installing over your 32-bit Windows) and enter information as requested. If you need access to your RAID array during the install process, then be sure to press F6 when it asks you, and load the driver off of the floppy disk you created.
If all goes well with the install Windows XP 64 should boot, and you can go and install all those handy driver files and software programs that you prepared in Step 2, and get your ethernet adapter working, and so on. Reboot your system after installing the updated drivers, and if windows successfully loads, then congratulations, your install was successful.
NOTE: Do not install the MSI LiveUpdate software from the CD, as I did this and when Windwos loaded I would get a message saying "The service is not started" and when I clicked "Ok" the system would spontaneously reboot. Disabling the software fixed this problem.
...I think that's all. Let me know if I've missed anything.

Quote
Originally posted by Some1ne
Here's a step-by-step description of how to install the RealTek RTL8169/8110 driver, as the process isn't quite as straightforward as it should be:
1. Download the Windows AMD64 Drivers available here:
http://www.realtek.com.tw/downloads/downloads1-3.aspx?series=16&Software=True
2. Extract the files in the archive to somewhere like c:\win64drivers\ethernet
3. Once inside Win XP 64, do the following:
a. Click Start -> Settings -> Control Panel -> System -> Hardware -> Device Manager
b. Go down to the "Other Devices" section (they'll have yellow ?'s)
c. Right click on the ethernet controller and click "Update Driver"
d. Click "Install from a list or specific location (Advanced)"
e. Click "Dont search. I will choose the driver to install."
f. Double click the "Network Adapter" entry, and then click "Have Disk..."
g. Select the directory which you extracted the driver files to
i. You will get messages saying that Windows cannot verify that the driver matches your hardware, and that the driver is not WHQL certified. Ignore these and click "Continue"/"Install Anyways" and your RealTek RTL8169/8110 ethernet adapter will spring to life
after i have done this the pc just stops. and if i reboot it stops at the loading screen :/ can you tell me whats wrong i got a k8t neo serie card and windows 64 bit edition
edit: i did it :D works now

Problem trying to install XP via Boot Camp, computer almost died

Hi there,
I just recently purchased a 24" 2.8Ghz intel iMac 500GB harddrive with OS X 10.5.2. I plugged everything together yesterday morning and the computer was going fine, just liek a dream. On a side note I was genuinely impressed with the ease of setting up and how quick, intuitive and reliable the mac and OS X Leopard was.
This is a bit long but I think I need to go into detail what happened in order for any of you to fully understand what happened to my mac.
Later in the afternoon I decided to install Win XP via Boot Camp. I knew that XP SP2 or later and VISTA was recommended but I decided to use my XP Home Edition "2002 version" install disc instead.
I opened up the Boot Camp Assistant, partitioned 15GB of the 500GB harddrive, inserted WinXP install disc and the computer restarted with everything going to plan thus far. I was going through the install process as normal but I came to a window asking which partition to use to install XP ("c" or "d") or if I wanted to create another partition. I also had my iPod still connected to the computer and I think the installation recognised that harddrive too (all 12GB of space left on my iPod). I wasn't sure what to do so I decided to quit the install process by pressing the relevent keys ("press F3 to quit" etc). Upon automatically restarting the computer I first came to a white screen for about1 or so minutes and then a black screen came up with white text asking me to "press any key to 'something' the CD" (can't remember what the rest of the text was), but the keyboard was unresponsive. I turned the computer off and unplugged it as according to the instruction manual that came with the mac, waited the suggested 5-6 seconds, turned it back on but I came across the same screens. I couldn't eject the XP install disc either. I restarted the computer again, held down the eject button whilst restarting, the disc thankfully ejected but I then came across the same black screen but with no text, just a white flashing underscore cursor. I decided to remove my iPod and restart the computer again. AGAIN I came across the same white screen, then black screen with the flashing white underscore cursor and unresponsive keyboard. I decided to insert the OS X install disc 1 (I don't remember if I inserted it whilst at the black screen or if I restarted the computer and THEN inserted the OS X install disc). The disc loaded slowly but I eventually went through the install process (choosing your language) and then came across a window asking me "Where would you like to install OS X?" but I couldn't install it anywhere. I opened "disk utility" or some program with the word "disk" in it, had no idea what I was doing, somehow created a new volume (though I thought I was actually erasing the XP partition I set up earlier) but in MS-DOS FAT Format or something. I then was able to choose a place (or volume) to install OS X but I had to change the format of the untitled volume from FAT to something along the lines of "Mac OS X journaled (enabled)" (whatever that means). There were other format options available but I just chose the top one on the list (Mac OS X journaled (enabled)). I then made a full install of OS X 10.5.2 and late last night downloaded the latest pdate for Leopard (10.5.4) along with other updates. The computer is working fine now thankfully andeverything seems to be back to normal.
I just want to know what actually happened. What did happen to my computer? Did I somehow wipe the harddrive? Why didn't the computer reboot to HDD when I ejected the WinXP install disc? Which format is the HDD formatted to? What does "Mac OS X journaled (enabled)" mean? Also how come my HDD is 500GB whereas when I checked Boot Camp Asistant a second time (but not installing Win XP again) My HDD is 460GB with 440GB of available space? Is there still another partition I am unable to see? Is there an extra 40GB of data floating around the harddrive that I'm unaware of? What are the factory settings for my computer? I really hope I haven't formatted the disk and installed the OS to settings that weren't like how the computer was originally set BEFORE I regrettably tried to install WinXP via Boot Camp.
If anyone could respond or give me some sort of advice, explanation or help I would very much appreciate your assistance.
Cheers.

According to wiki "the documentation from Apple states that Windows XP Service Pack 2 or Windows Vista is requisite for a Boot Camp installation, and it also mentions that trying to install an unsupported operating system could prevent the computer from booting even into Mac OS X". Sure that was from wiki, but it does seem to support and somewhat validate the problem I had with installing an earlier edition of XP.
http://en.wikipedia.org/wiki/BootCamp_%28software%29#Other_operatingsystems
Thanks for the info on the Filesystem info. My problem is that installing OS X on a mac is just a little bit more technical than installing Windows on a PC as there are a few more things to consider. Plus I'm not familiar with any of the utility programs as well. It's a **** miracle I managed to somehow create a volume to install OS X on when I thought I was erasing the partition I created for WinXP.
But I'm still not sure about the missing 40GB from my 500GB HDD. Upon coming to the desktop straight after OS X was fully re-installed I noticed that the HDD only had 460GB and that 440GB of it available space. So the full installation of OS X was 20GB, but where has the other 40GB gone? I swear I saw that I had much more available space on my harddrive (BEFORE I tried to partition my HDD under Boot Camp Assistant and stuffing up the computer). Is the missing 40GB from the ORIGINAL FACTORY INSTALL of OS X INCLUDING all my iTunes music and other files I uploaded to the computer earlier? It would make sense but there's no way, as far as I know, of checking this. Any ideas?
Cheers.

I'm installing windows 7 64-bit on my imac which I've done before but I get a message that the partition is GPT even after I format the bootcamp partition. I just upgraded my hard drive to a 3tb and I'm allocating 1tb for windows. How can I fix this?

I'm installing windows 7 64-bit on my imac which I've done before but I get a message that the partition is GPT even after I format the bootcamp partition. I just upgraded my hard drive to a 3tb and I'm allocating 1tb for windows. How can I fix this?

No easy fix for a few reasons:
1) Bootcamp requires a hybrid MBR for the partition table. That is: both an MBR and a GPT partition table at the same time with the GPT one having all partitions and the MBR one having only the ones that are relevant, but at most 4 of them (including the protective partition and the Macintosh HD one). Which leads us to:
2) The MBR part of the hybrid partition table cannot work with 3TB hard drives. MBR is limited to 2TB.
I am working on a small EFI app that can boot Windows in EFI mode on a Mac and that would mean that you can go GPT only on your system. The progress of the app is slow due to the nature of EFI and for now requires that you do an unattended Windows install with slipstreamed graphics drivers, but we are adding VGA loading on top of EFI quite soon after the rest of the app stabilises. The status of the app is documented at:
Win7 x64 booting natively via EFI (no bios emulation)
Windows does actually successfully boot in EFI mode on most Macs (anything with a 64bit EFI should work), but does not have graphics support even if you load the driver due to the VGA pci registers not being set by the firmware. Furthermore, in Setup and Safe Mode, Windows uses VGA instead of GOP which is a failure by design since VGA is a BIOS standard and not really compatible without hacks with EFI. Other EFI implementations also add VGA compatibility at a high cost to the firmware complexity for the VGA cards available on the market that don't actually contain anything in their ROM except the VGA BIOS.
My recomendations:
1) Install on a second smaller hard-drive; or
2) Wait for the EFI app to come out officially and use that to boot Windows Vista SP1 x64 and Windows 7 x64 (RTM and SP1) in the native EFI mode.
3) Wait for Windows 8 which supports VGA-less booting acording to the AMD presentation at UEFI Plugfest.

Trying to install windows 7 64 bit on a mac mini

I'm trying to install windows 7 64 bit on a mac mini, via boot camp. Install hangs at about 10% while files are being loaded from windows disc. I'm using an LG USB 2.0 Super-Multi DVD Burner. What's the fix for this.

Check this out: Boot Camp- Macs that work with 64-bit editions of Microsoft Windows Vista and Windows 7

Installing Arch64 using VirtualBox?

Hey,
I wanna install Arch64 on a raw disk on my Core 2 Duo computer, using VirtualBox (I am currently using Arch i686).
There is a wiki article describing how to do so:http://wiki.archlinux.org/index.php/Installing_Arch_Linux_from_VirtualBox
Question is whether I can install Arch64 using an Arch i686 host (with VirtualBox)?
Thanks
fiod

You can run a 64 bit guest on a 32 bit OS. Check the below link for full details.
http://www.virtualbox.org/manual/UserMa … 4bitguests
As far as I know using physical disk partitions for VMs is possible but not supported.

How to Install Coldfusion 8 64-bit on Small Business Server 2008 64-bit

How to Install Coldfusion 8 64-bit on Small Business Server 2008 64-bit
I ran Coldfusion 8 on SBS 2003 Premium for 6 months with no problems. When we finally decided to cut over to SBS 2008, that’s when everything went to hell. I tried for weeks to get Coldfusion 8 to install properly on the new SBS 2008 64-bit box. During the course which, I found bits and pieces of information for Vista 64-bit and Windows Server 2008 64-bit installations. There are some distinct differences, however, with SBS 2008 since it runs core Web applications like OWA, RWW and Companyweb. After countless unsuccessful attempts, one of which completed corrupted the box, I found the solution.
I have attempted in this white paper to detail the steps to assist others who may be in a similar situation. I don’t make any warranty for the information, but so long as you follow the steps carefully you should be fine. BTW, for those of you who say Adobe offers free technical support for licensed users, that’s not entirely true. Like I said, I purchased CF8 and originally installed it on an SBS 2003 Premium box. After we cut over to SBS 2008 and encountered problems, Adobe wouldn’t provide any technical support without charging. Moreover, based on my initial conversations with Adobe’s technical team, no one seemed to know much about running 64-bit on SBS.
From my understanding, only two versions of Coldfusion 8 can be installed in 64-bit: Enterprise and Developer. The “normal” install (which I paid a grand for) can only be deployed in 32-bit mode – gee, THANKS Adobe! By the way, in Developer mode only two distinct IPs can access the site in addition to the localhost. Any additional IPs will result in a CFML error message stating that the maximum number of IPs have been exceeded. At any rate, take your time and follow the steps to achieve a successful installation.
PRE-INSTALLATION TASKS
Back Up SBS
It’s always a good practice to backup your server before deploying any kind of major system changes. Although this step is optional, I recommend it in case you need to restore your server for any reason. Bear in mind, if your system ever gets totally corrupted, you cannot restore back from the twice daily incremental backup images alone. You will need a full backup with system recovery information to restore. Here are the basic steps:
Click: Start > Programs > Administrative Tools. Right-click “Windows Server Backup” and choose “Run as administrator”.
Click “Backup Once” under Actions in the right-hand pane.
Choose the “Different Options” radio button under Backup Options.
Choose the “Custom” radio button. What we’re primarily interested in here is backing up the OS – not your data partitions or attached drives.
Select the “SYSTEM (C)” checkbox, uncheck any others. Also, ensure that the “Enable system recovery” checkbox is selected before continuing on.
Under ‘Specify Destination Type’, I usually select the “Local drives” radio button and point it to a Terrabyte USB drive I use for backups. You can point this to a tape drive, or select the “Remote shared folder” radio button if you map to a UNC path to store your backup images. Just remember, make sure that whatever path you select can readily be accessed in the event of an emergency. Also, make sure the “Verify after writing (recommended)” checkbox is selected.
Under ‘Specified Advanced Option’, I usually select the “VSS full backup” radio button instead of the default since I don’t use a 3rd party backup product. If like me you rely solely on SBS for your backups, choose the full backup option.
Confirm everything and click “Backup”. This process may take several hours depending on the size of your system.
Verify ISAPI Filters:
In IIS Manager, double-click the server instance in the left-hand pane.
In the center pane under IIS, double click the “Modules” icon to verify that the ISAPI native modules are already installed for IIS. If it’s set up correctly you should see two entries:
IsapiFilterModule %windir%\System32\inetsrv\filter.dll
IsapiModule %windir%\System32\inetsrv\isapi.dll
If either of these modules are missing, you will need to re-install these (google for a solution).
Set Up Development Environment
Create a directory for your CFML files outside of the default Windows location (e.g., default is usually C:\inetpub\wwwroot\). For the purpose of our install, I created a directory on a separate disk called: D:\DEV.
Copy and paste your CFML files and directories into the new DEV root Web directory. This will eventually be the directory where the Coldfusion installer places the CFIDE and CFDOCS folders.
Open IIS Manager and double-click the server instance in the left hand pane. Expand the “Sites” folder. Right-click the Sites folder and select “Add Web Site”.
Enter a name in the “Site Name” box (e.g., “test-site”). You will notice that the system will automatically create a corresponding Application Pool with the same name. NOTE: this is important to prevent conflicts between the DefaultAppPool (needed for SBS Web apps like OWA, RWW, etc.) and the application pool needed for Coldfusion to function properly in SBS 2008.
Point the “Physical Path” to the directory you created in step #1 above (e.g., “D:\DEV”).
Don’t worry about testing the connection. If you click “Test Settings” you may receive a warning that IIS cannot verify access to path (D:\DEV). Don’t worry about this for the time being.
Under “Host name”, enter a DNS path to your site (e.g., “dev.test-site.com”). Click “OK”.
Configure Application Pools for Installation
In IIS Manager, double-click the server instance in the left-hand pane. Click on “Application Pools” to display the list of server application pools in the center pane.
In the “Actions” pane on the right-hand side, click “Set Application Pool Defaults”.
Change “Enable 32-Bit Applications” - the second item from the top – from “False” to “True”, and then click “OK”. NOTE: if you skip this step, Coldfusion will not properly create the required mappings during the install. We will change this setting back after the installation completes – more on this later.
Modify the application.host.config File for 64-Bitness
Click: Start > Programs > Accessories. Right-click “Notepad” and choose “Run as administrator”.
Open the config file from within Notepad – default location: C:\Windows\System32\inetsrv\config\applicationHost.config
Do a search and change this one line from:
<add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" />
To this:
<add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" preCondition="bitness64" />
Restart the IIS Admin service.
Set HTTP Compression
According to some threads I read, the http compression module can cause errors if you don’t disable it globally. To remedy this, perform the following:
Click: Start > Programs > Accessories. Right-click “Command Prompt” and choose “Run as administrator”.
At the command prompt, change directory to intetsrv by typing: cd inetsrv
Run the following command:
C:\Windows\system32\inetsrv>appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
This will turn off HTTP compression for all sites in IIS.
In IIS Manager, double-click the server instance in the left-hand pane. Double-click the “Compression” icon in the IIS section of the center pane.
Uncheck all of the boxes, then click the “Apply” button under Actions in the right-hand pane.
Recheck all of the boxes, then click the “Apply” button under Actions in the right-hand pane.
Restart the IIS Admin service. This should enable compression and coldfusion to work at the same time.
NOTE: if for some reason you need to reverse this, run the following command from the command prompt:
C:\Windows\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+[name='xpress',doStaticCompression='false',dll='%windir%\system32\inetsrv\suscomp.dll']
INSTALLATION TASKS
Download the 64-bit installation package from Adobe – filename: coldfusion-801-wind64.exe.
Right-click the file and select “Run as administrator”.
Accept the terms of the License Agreement.
If you have an Enterprise license, enter it. For our purposes, just click the “Developer Edition” checkbox.
Select “Server configuration” – the default radio button.
I deselected all subcomponents and can’t guarantee that you’ll arrive at the same results if you select additional items like “.NET Integrated Services”. It should be fine, particularly if you install documentation. My preference was to keep the install as plain vanilla as possible.
Select the directory path for Coldfusion to install into – default is :C\Coldfusion
THE NEXT TWO STEPS ARE CRITICAL TO YOUR SUCCESS. Unselect “All IIS Websites” and select the “Configure specific IIS Website or another web server” radio button. Click “Add”, and then select your test Web site (e.g., “test-site”) under “IIS Web Site”. Hit “OK”.
Do NOT use the default directory path for the CF Administrator location (e.g., default path: “C:\inetpub\wwwroot”). Instead, point the installer to your new DEV root Web directory (e.g., “D:\DEV”). The bottom line, you want the installer to place the CFIDE directory and files within this folder, alongside your other CFML files and folders.
Enter an Administrator password.
Choose to Enable RDS, or not. I enable this by preference but it is not required. This allows you to make updates to files using a CFML editor directly vs. having to move/FTP the files over if you’re working remotely. Opponents to this argue that it’s potentially less secure, but for a lower environment I don’t see this as a major concern.
Confirm everything to kick off the install.
If all goes well you should see a message at the end stating that the install was successful. I recommend you uncheck the box that asks you to open the CF Administrator in the default Web browser after the install. NOTE: we will open it a different way during the post-installation tasks. The worst thing that will happen if you forget to uncheck the box is that you might receive an error that the command prompt hung – not a big deal – just close it and move on to the next (final) steps.
POST-INSTALLATION TASKS
Verify CF Installation:
The installation will create a new folder in your program group: Start > Programs > Adobe > Coldfusion 8. The default “Administrator” link will not work because it points to the wrong path: http://127.0.0.1/CFIDE/administrator/index.cfm. The “127.0.0.1” or “localhost” path as you may recall in IIS, points by default to the “C:\inetpub\wwwroot” directory. Our CFIDE files, however, are located within: D:\DEV.
To bring up the CF Administrator logon page, open up a Web browser and replace the “http://127.0.0.1” part of the path with the DNS path name to your CF environment (e.g., http://dev.test-site.com/CFIDE/administrator/index.cfm).
This should bring up the Coldfusion Administrator Login screen. Enter in the Administrator password you created during the install to log in and configure your application server.
Verify that your test-site renders correctly by typing in your test URL into a Web browser (e.g., http://dev.test-site.com).
Fix Application Pool Defaults to Re-enable SBS Web Applications:
At this point, Coldfusion Administrator and your test CMFL Web site should be working properly. The problem is, default SBS Web applications like OWA, RWW and Companyweb will throw errors and fail to start. Fortunately, this is easily remedied by performing the following steps:
In IIS Manager, double-click the server instance in the left-hand pane. Click on “Application Pools” to display the list of server application pools in the center pane.
In the “Actions” pane on the right-hand side, click “Set Application Pool Defaults”.
Change “Enable 32-Bit Applications” - the second item from the top – from “True” to “False” this time. This should re-enable the SBS applications, which would otherwise result in 500 errors (e.g., OWA, RWW, Companyweb, etc.). There is no need to restart IIS.
Open a Web browser and test that you can once again connect to OWA, RWW and Companyweb successfully.
In IIS click to highlight the application pool for your new site (e.g., “test-site”). In the right-hand pane, click “Advanced Settings”. Ensure that “Enable 32-Bit Applications” – second item from the top – is set to “True” for this application pool specifically.
Lastly, jump up and down for joy! Hopefully now, everything is working. Best of luck!! ..Paul D (MCP).

First, it would be a good idea for you to specify what distro of Linux you're using, as not all are supported by Adobe.
Second, this is probably your problem right here:
http://askubuntu.com/questions/40416/why-is-lib-libc-so-6-missing
In a nutshell, CF expects the 32-bit version of libc.so.6 to be in /lib, but it's probably not. You might be able to modify the installer to point to the correct location for that file, or you might be able to create a symlink to the file - but as the above link describes, creating a symlink might have negative consequences.
As for installing CF 8 64-bit, that's only available with Enterprise, not Standard. If you want CF Standard 64-bit, you need to upgrade to CF 9.
Dave Watts, CTO, Fig Leaf Software

Cannot install Windows 7 32-bit using Boot Camp

I have one of the new iMacs (late 2012) and I can't install Windows 7 32-bit using Boot Camp. Whenever I try to being the installation using the Boot Camp Assistant, I always get the following message: "Need 64-bit Windows installation USB drive or DVD. Boot Camp only supports 64-bit Windows installation on this platform. Please use an USB drive or DVD which contains 64-bit Windows". I have successfully installed 32-bit Windows on my Macbook Pro that is running the same version of Mac OS X and Boot Camp, but I don't know why on this new iMac it doesn't allow me to. Apple's documentation states that I should be able to install either 32-bit and 64-bit without any problem, but this is not the case here. I can't find anything about this problem/error on the Internet either. HELP!!!

AidenT wrote:
Yes, circumstances do change but if Apple is, as they claim to be, serious about seamlessly migrating what is still a large and dominant market share of users from Windows, supporting 32 bit versions is not a nice to have, but a must have.
I don't see why users have to make excuses when there is a clear shortfall of what is promised.
In other discussions, there is talk of an opportunity for Apple to make a significant impact, as Windows 8 has deviated so much from the comfort zone of traditional Windows users. But to make that change, Macs have to support what is still a primarily 32 bit environment in the installed base.
As for the use of VMs, I had a tough time migrating out of Parallels 6 after an upgrade to Mountain Lion broke compatibility so IMHO it is not a long term solution unless you are happy to hand out $50 every 2-3 years just to support the same functionality.
Use Virtual Box, it's free.
32 bit may have a reasonable user base but it's going away fast, if you must use 32 bit Windows and won't use a VM your choice is limited.
Buy a PC, or buy an older Mac.
The rest of your post is speculative and I won't go there.

How to install windows 7 32 bit virtual machine on windows 7 64 bit

Wondering what would be involved in installing windows 7 32 bit as a virtual machine on a windows 7 64 bit laptop, trying to continue to use software that only has 32 bit drivers to talk to specialized hardware before scrapping the hardware. Drivers
are not updateable due to the company no longer exist. Being forced to do this since I am using windows XP to currently do this and will have to stop using XP by 01Apr2014.
thanks for any help

If it's special hardware, your chances are small for it to work in a
virtual machine. Some USB devices might work, but Virtual PC can't see
the real hardware on the host.
Bob Comer Microsoft MVP -- Hyper-V

Install coldfusion 8 32 bit on 64bit system

in agreement with docs
http://kb2.adobe.com/cps/403/kb403277.html#main__Toc193176416
("As of ColdFusion 8 Update 1, the Standard Edition can run as a 32-bit application on all supported 64-bit platforms in addition to 32-bit platforms")
i'm trying to install coldfusion-801-lin.bin on
a linux 64bit system
but i receive this error
[root@lnx1 store]# ./coldfusion-801-lin.bin
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
strings: '/lib/libc.so.6': No such file
Launching installer...
./coldfusion-801-lin.bin: /tmp/install.dir.9137/Linux/resource/jre/bin/java: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
./coldfusion-801-lin.bin: line 2479: /tmp/install.dir.9137/Linux/resource/jre/bin/java: Success
=========
if i tryng to install coldfusion-801 64bit version,
the serial number is not valid
(my serial number is CF standard, upg license)
you can help me?
many thanks!

First, it would be a good idea for you to specify what distro of Linux you're using, as not all are supported by Adobe.
Second, this is probably your problem right here:
http://askubuntu.com/questions/40416/why-is-lib-libc-so-6-missing
In a nutshell, CF expects the 32-bit version of libc.so.6 to be in /lib, but it's probably not. You might be able to modify the installer to point to the correct location for that file, or you might be able to create a symlink to the file - but as the above link describes, creating a symlink might have negative consequences.
As for installing CF 8 64-bit, that's only available with Enterprise, not Standard. If you want CF Standard 64-bit, you need to upgrade to CF 9.
Dave Watts, CTO, Fig Leaf Software

Unable to install Adobe CS5 64 bit package created using Adobe Application Manager on Windows 7 64

I am unable to install Adobe CS5 64 bit package created using Adobe Application Manager on Windows 7 64 bit.Basically installation rollback on Win 7 64 bit image.
MSI Log File :-
Property(S): ProductToBeRegistered = 1
MSI (s) (5C:D4) [17:59:21:784]: Note: 1: 1708
MSI (s) (5C:D4) [17:59:21:784]: Product: Adobe_CreativieSuite_5_MNT -- Installation operation failed.
MSI (s) (5C:D4) [17:59:21:784]: Windows Installer installed the product. Product Name: Adobe_CreativieSuite_5_MNT. Product Version: 1.2.0000. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Installation success or error status: 1603.
Please let me how to install 64 bit package on Win7 64 bit.
Thanks in Advance.

Ok so I downloaded the most current installer CS5.1, My previous installer was version 5.0. It did install fine fully updated to my license version. I just wanted to update in case anyone in the future has a similiar experience. Too bad this advice was not offered by the "experts" here.

I can not use my mouse or keyboard when I am trying to install windows via boot camp

Please can you help!
I can not use my mouse or keyboard when I am trying to install windows via boot camp

Starting a couple of days ago my mouse and keyboard stopped working suddenly.
How are they connected? In my case they are wireless and their receiver is plugged into my USB hub. After an update I found the OS inexplicably not recognizing my USB hub and hence any devices which were plugged into it. My fix was to
plug the receiver into a different USB port (so I could use the mouse and keyboard; otherwise I would have had to use the OSK via Touch or pen.) Once I had normal access into my machine again I used Device Manager to remove all USB controller and
hubs (including hidden ones) and I then shut down, disconnected all USB devices and powered back up, this time using only Touch to get going. Once the OS had settled down I started plugging stuff back in the way that I wanted it to be recognized.
If I didn't have Touch I would have had to have left the wireless receiver plugged in both places which I assume would be OK. I have no idea why updates have such a catastrophic effect for USB devices.
Robert Aldwinckle

Is there a way to install just the 32 bit version of Photoshop CS5 on a Windows 7 64 bit machine?

I have a custom built Java 6 application that doesn't like Photoshop CS5 64 bit edition. The program copies over a file from the network to the local machine and then opens it in Photoshop. The user manipulates the image and saves the changes. The user then completes the image and the application copies the image back to the server. The problem we're having is: When we use Photoshop CS5 64-bit, it takes about 2 minutes for Photoshop to open the image. The file is copied over within 2 seconds and the Photoshop icon on the windows taskbar starts flashing. But then you spend a few minutes waiting for it to open.
Some things that I have tried to isolate the problem:
- I found you can copy the file somewhere else, double click on it and the image will open in Photoshop before the script is able to open the file.
- I tried uninstalling Photoshop and reinstalling just the 64 bit edition without the 32 bit installation. The script just stops working in this situation.
- I tried uninstalling CS5 and installing CS3. The image opens as soon as the file is copied over.
What I would like to try next is to install just the CS5 32 bit version. But the installer is being uncooperative and will only allow either the 64 bit version or both the 64 and 32 bit versions. So, back to my question: Is there a way to install just the 32 bit version of Photoshop CS5 on a Windows 7 64 bit machine?

Do you mean schroot? If so I'm not sure exactly how well that will work out, because the part that depends on python is a deamon that handles communication between the USB dongle and the Tux Droid which may mean hacking the deamon a bit so ether way this does not seem like it will be a easy task.

ITunes will not install on a 64 bit PC Win 7

iTunes will not install on a 64 bit PC running Windows 7 with all updates.
Most answers send you to a "cleaner" of somekind that check for errors in you PC and then wants to charge you to clean it. My PC is CLEAN.
Something is keeping iTunes from installing and running. Tried 64 bit, 32 bit and all help desks.
Same error message "This version is for a 32 bit computer, yours is a 64 bit!" I know that and only install the 64 bit version!!!

Same error message "This version is for a 32 bit computer, yours is a 64 bit!"
Doublechecking ... by any chance did you migrate a 32-bit version of the iTunes, Apple Mobile Device Support and Bonjour programs to the 64-bit machine from a 32-bit machine using the PC Mover utility?
(Your symptoms are consistent with that ... the installer service throws the message when trying to uninstall the 32-bit itunes and related 32-bit componentry prior to installing the new 64-bit versions.)

Installing Arch64 via 32-bit vm

Similar Messages

Maybe you are looking for