32 bit application on 64 bit Vista

"Richard G. Harper" <rgharper@email.com> wrote in message
news:OTRJzhgoIHA.1768@TK2MSFTNGP03.phx.gbl...
> Almost certainly not, since in this specific case the software (VPN
> Client) needs to install a device driver component to work correctly. You
> cannot force 32-bit drivers to work in a 64-bit environment. This was
> true in 64-bit XP and continues to be true under Vista. Contact Cisco for
> a 64-bit version of the client or drop back to 32-bit Vista.
>


I appreciate the feedback on this.

I'm afraid I got myself caught in a mess. I bought a PC with 4 GB of RAM
and accepted advice that I needed to order the 64 bit OS in order to be able
to use the memory I bought. Now I realize I cannot run a really important
productivity application without having to buy a second OS and go through
the hassle of installing Vista 32 on a brand new Vista 64 PC.

I will assume that I will have to completely wipe out the partitions on the
hard drive (the recovery partition that came with the PC and the system
partition) and create a new system partition to install the 32 bit version
of Windows.

Surely not a 5 minute task! Frustrating! :-(

Of course, to add insult to injury, I will have paid for a GB of memory that
I will go mostly unused.

"John Smith" <someone@microsoft.com> wrote in message
news:nIidnTRiyqN87ZfVnZ2dnUVZ_oGjnZ2d@comcast.com. ..
> "Richard G. Harper" <rgharper@email.com> wrote in message
> news:OTRJzhgoIHA.1768@TK2MSFTNGP03.phx.gbl...
>> Almost certainly not, since in this specific case the software (VPN
>> Client) needs to install a device driver component to work correctly.
>> You cannot force 32-bit drivers to work in a 64-bit environment. This
>> was true in 64-bit XP and continues to be true under Vista. Contact
>> Cisco for a 64-bit version of the client or drop back to 32-bit Vista.
>>
>
>
> I appreciate the feedback on this.
>
> I'm afraid I got myself caught in a mess. I bought a PC with 4 GB of RAM
> and accepted advice that I needed to order the 64 bit OS in order to be
> able to use the memory I bought. Now I realize I cannot run a really
> important productivity application without having to buy a second OS and
> go through the hassle of installing Vista 32 on a brand new Vista 64 PC.
>
> I will assume that I will have to completely wipe out the partitions on
> the hard drive (the recovery partition that came with the PC and the
> system partition) and create a new system partition to install the 32 bit
> version of Windows.
>
> Surely not a 5 minute task! Frustrating! :-(
>
> Of course, to add insult to injury, I will have paid for a GB of memory
> that I will go mostly unused.

What you might want to do is boot 64 bit. Make the recovery CD/DVDs per OEM
instructions.

If your OEM included CD/DVD on the side like my Acer did, they are 32 bit.
Then install those. But consider to leave the recovery partition alone. In
my case, 9GB or so. Just in case by some miracle Microsoft gets their
collective crap together. Say a free downgrade to XP Pro x64 or upgrade to
Win7 flavour of the day.

2 other possibilities. I have had luck with VirtualBox.
http://www.virtualbox.org/ In virtual box just load a copy of XP. In
Vista, make sure you bridge the networks, it is in the docs but not readily
apparent. The best part of this approach is you get XP and Vista.

Just finished doing something like this with my new (PoC Vista) box. Didn't
want to wipe out Vista just in case. So I left it there. I suspect the
following will work if you have 2 drives. It is similar to what I am doing
but I am doing it with 2 Linux and one Vista.

1) Have Vista OEM of one version or another running. Deallocate the second
disk if allocated.
2) Shrink the disk partition leaving 1/2 the space on the first disk.
3) Load XP into the open space on the second disk.
4) Load Fedora 8 or 9 or Ubuntu into the open space on the first disk. When
doing this, add the Vista and XP partition to boot.

Leave the recover partition alone if you can. This will allow for recovery
of the original Vista x64.

By loading Linux last, you get the Linux Grub bootloader which will replace
the brain dead MS ones. It is far superior to the mono-inbread Vista
version. It can boot Vista not-so Premium and XP and Linux and others.
Grub isn't a racist bootloader.

Best of all worlds.

Now for Frank, my pet ms-dog...

"John Smith" <someone@microsoft.com> wrote in message
news:nIidnTRiyqN87ZfVnZ2dnUVZ_oGjnZ2d@comcast.com. ..
> I will assume that I will have to completely wipe out the partitions on
> the hard drive (the recovery partition that came with the PC and the
> system partition) and create a new system partition to install the 32 bit
> version of Windows.

No. You could just partition the drive and install Vista 32 alongside
Vista 64.

Or you can what I do. I run XP inside Virtual PC on my Vista 64 machine.
All of my work stuff (Visual Studio, Crystal Reports, SQL Server, VPN
connection, Outlook email, etc. etc.) is all running on XP in VPC. This
gives the added benefit that only the XP machine is tied to the VPN
connection to the office, not my whole machine. Outside of this single
Virtual machine, I have full internet access without going thru the company
network.

Very handy and clean solution. Plus back up and restore the Virtual hard
disk is a breeze. Virtual PC is a free download from MS.

Canuck57 wrote:
> "John Smith" <someone@microsoft.com> wrote in message
> news:nIidnTRiyqN87ZfVnZ2dnUVZ_oGjnZ2d@comcast.com. ..
>
>>"Richard G. Harper" <rgharper@email.com> wrote in message
>>news:OTRJzhgoIHA.1768@TK2MSFTNGP03.phx.gbl...
>>
>>>Almost certainly not, since in this specific case the software (VPN
>>>Client) needs to install a device driver component to work correctly.
>>>You cannot force 32-bit drivers to work in a 64-bit environment. This
>>>was true in 64-bit XP and continues to be true under Vista. Contact
>>>Cisco for a 64-bit version of the client or drop back to 32-bit Vista.
>>>
>>
>>
>>I appreciate the feedback on this.
>>
>>I'm afraid I got myself caught in a mess. I bought a PC with 4 GB of RAM
>>and accepted advice that I needed to order the 64 bit OS in order to be
>>able to use the memory I bought. Now I realize I cannot run a really
>>important productivity application without having to buy a second OS and
>>go through the hassle of installing Vista 32 on a brand new Vista 64 PC.
>>
>>I will assume that I will have to completely wipe out the partitions on
>>the hard drive (the recovery partition that came with the PC and the
>>system partition) and create a new system partition to install the 32 bit
>>version of Windows.
>>
>>Surely not a 5 minute task! Frustrating! :-(
>>
>>Of course, to add insult to injury, I will have paid for a GB of memory
>>that I will go mostly unused.
>
>
> What you might want to do is boot 64 bit. Make the recovery CD/DVDs per OEM
> instructions.
>
> If your OEM included CD/DVD on the side like my Acer did, they are 32 bit.
> Then install those. But consider to leave the recovery partition alone. In
> my case, 9GB or so. Just in case by some miracle Microsoft gets their
> collective crap together. Say a free downgrade to XP Pro x64 or upgrade to
> Win7 flavour of the day.
>
> 2 other possibilities. I have had luck with VirtualBox.
> http://www.virtualbox.org/ In virtual box just load a copy of XP. In
> Vista, make sure you bridge the networks, it is in the docs but not readily
> apparent. The best part of this approach is you get XP and Vista.
>
> Just finished doing something like this with my new (PoC Vista) box. Didn't
> want to wipe out Vista just in case. So I left it there. I suspect the
> following will work if you have 2 drives. It is similar to what I am doing
> but I am doing it with 2 Linux and one Vista.
>
> 1) Have Vista OEM of one version or another running. Deallocate the second
> disk if allocated.
> 2) Shrink the disk partition leaving 1/2 the space on the first disk.
> 3) Load XP into the open space on the second disk.
> 4) Load Fedora 8 or 9 or Ubuntu into the open space on the first disk. When
> doing this, add the Vista and XP partition to boot.
>
> Leave the recover partition alone if you can. This will allow for recovery
> of the original Vista x64.
>
> By loading Linux last, you get the Linux Grub bootloader which will replace
> the brain dead MS ones. It is far superior to the mono-inbread Vista
> version. It can boot Vista not-so Premium and XP and Linux and others.
> Grub isn't a racist bootloader.

Grub is a real piece of sh*t bootload that will totally destroy any and
all Windows bootloaders. And when you delete linux, (which 99.99% of all
those who try linux eventually end up doing) you have to make sure you
manually remove all traces of grub (where do they get those stupid names
from any way?) before deleting linux or else you cannot repair Vista bcd
downloader using the repair option from the Vista DVD. It won't work!
Best to load linix on a completely separate HDD with all of the other
HDD unplugged. Then you can plug them in after the install and use the
BIOS or your keyboard (F8 on some of mine) to load whichever OS you want.

BTW, which "productivity application" won't run on Vista x64?

>
> Best of all worlds.
>
> Now for Frank, who will telly ou the real truth....

I see you're once again passing out info that is meant to destroy
Windows for unsuspecting users.
Shame on you...LOL!
Frank

"Bob Campbell" <bob@bob.bob> wrote in message
news:GOydnYlCvvQ_G5fVnZ2dnUVZ_oaonZ2d@supernews.co m...
> "John Smith" <someone@microsoft.com> wrote in message
> news:nIidnTRiyqN87ZfVnZ2dnUVZ_oGjnZ2d@comcast.com. ..
>> I will assume that I will have to completely wipe out the partitions on
>> the hard drive (the recovery partition that came with the PC and the
>> system partition) and create a new system partition to install the 32 bit
>> version of Windows.
>
> No. You could just partition the drive and install Vista 32 alongside
> Vista 64.
>
> Or you can what I do. I run XP inside Virtual PC on my Vista 64 machine.
> All of my work stuff (Visual Studio, Crystal Reports, SQL Server, VPN
> connection, Outlook email, etc. etc.) is all running on XP in VPC. This
> gives the added benefit that only the XP machine is tied to the VPN
> connection to the office, not my whole machine. Outside of this single
> Virtual machine, I have full internet access without going thru the
> company network.
>
> Very handy and clean solution. Plus back up and restore the Virtual hard
> disk is a breeze. Virtual PC is a free download from MS.

Sounds like a good suggestion.

Before I buy a new Windows Vista 32 license, I think I will contact the
manufacturer. Their price for Vista 32 was the same as Vista 64. Perhaps
if I explain the dilemma (they partially contributed to my problem because
their online configurator instructs buyers to opt for the 64 bit OS when
purchasing the 4GB memory) they might ship me a Vista 32 set of disks. I
would very much like to install the Vista 32 alongside the Vista 64.

After I get the 32 bit OS, I will figure out how to install it, and use it.
I surmise I will have to have some dual boot option - boot the 32 bit OS
whenever I telework, the 64 bit OS the rest of the time. I only telework
once a week so I will be using the VPN client about 15% of the time.

"John Smith" <someone@microsoft.com> wrote in message
news:8ZWdnZ7HmKOEJ5fVnZ2dnUVZ_hmtnZ2d@comcast.com. ..
> After I get the 32 bit OS, I will figure out how to install it, and use
> it. I surmise I will have to have some dual boot option - boot the 32 bit
> OS whenever I telework, the 64 bit OS the rest of the time. I only
> telework once a week so I will be using the VPN client about 15% of the
> time.

All you have to do is partition your disk. You can do this right in
Vista - Control Panel, Computer Management, Disk Management. Right click
on the disk under the blue line and select Shrink Volume. Shrink it down
by whatever amount you want, but create enough free space to hold Vista 32
and whatever apps you need. This will leave empty space with a black line
on top. Right click in this space and choose Create new volume. Format
it and name it Vista32.

Now just boot the Vista 32 DVD and install it on the new partition you just
created. The dual boot will be setup automatically with your existing
Vista 64.

"Frank" <fb@jr.kmo> wrote in message
news:upVttIooIHA.5836@TK2MSFTNGP04.phx.gbl...
> Canuck57 wrote:
>> "John Smith" <someone@microsoft.com> wrote in message
>> news:nIidnTRiyqN87ZfVnZ2dnUVZ_oGjnZ2d@comcast.com. ..
>>
>>>"Richard G. Harper" <rgharper@email.com> wrote in message
>>>news:OTRJzhgoIHA.1768@TK2MSFTNGP03.phx.gbl...
>>>
>>>>Almost certainly not, since in this specific case the software (VPN
>>>>Client) needs to install a device driver component to work correctly.
>>>>You cannot force 32-bit drivers to work in a 64-bit environment. This
>>>>was true in 64-bit XP and continues to be true under Vista. Contact
>>>>Cisco for a 64-bit version of the client or drop back to 32-bit Vista.
>>>>
>>>
>>>
>>>I appreciate the feedback on this.
>>>
>>>I'm afraid I got myself caught in a mess. I bought a PC with 4 GB of RAM
>>>and accepted advice that I needed to order the 64 bit OS in order to be
>>>able to use the memory I bought. Now I realize I cannot run a really
>>>important productivity application without having to buy a second OS and
>>>go through the hassle of installing Vista 32 on a brand new Vista 64 PC.
>>>
>>>I will assume that I will have to completely wipe out the partitions on
>>>the hard drive (the recovery partition that came with the PC and the
>>>system partition) and create a new system partition to install the 32 bit
>>>version of Windows.
>>>
>>>Surely not a 5 minute task! Frustrating! :-(
>>>
>>>Of course, to add insult to injury, I will have paid for a GB of memory
>>>that I will go mostly unused.
>>
>>
>> What you might want to do is boot 64 bit. Make the recovery CD/DVDs per
>> OEM instructions.
>>
>> If your OEM included CD/DVD on the side like my Acer did, they are 32
>> bit. Then install those. But consider to leave the recovery partition
>> alone. In my case, 9GB or so. Just in case by some miracle Microsoft
>> gets their collective crap together. Say a free downgrade to XP Pro x64
>> or upgrade to Win7 flavour of the day.
>>
>> 2 other possibilities. I have had luck with VirtualBox.
>> http://www.virtualbox.org/ In virtual box just load a copy of XP. In
>> Vista, make sure you bridge the networks, it is in the docs but not
>> readily apparent. The best part of this approach is you get XP and
>> Vista.
>>
>> Just finished doing something like this with my new (PoC Vista) box.
>> Didn't want to wipe out Vista just in case. So I left it there. I
>> suspect the following will work if you have 2 drives. It is similar to
>> what I am doing but I am doing it with 2 Linux and one Vista.
>>
>> 1) Have Vista OEM of one version or another running. Deallocate the
>> second disk if allocated.
>> 2) Shrink the disk partition leaving 1/2 the space on the first disk.
>> 3) Load XP into the open space on the second disk.
>> 4) Load Fedora 8 or 9 or Ubuntu into the open space on the first disk.
>> When doing this, add the Vista and XP partition to boot.
>>
>> Leave the recover partition alone if you can. This will allow for
>> recovery of the original Vista x64.
>>
>> By loading Linux last, you get the Linux Grub bootloader which will
>> replace the brain dead MS ones. It is far superior to the mono-inbread
>> Vista version. It can boot Vista not-so Premium and XP and Linux and
>> others. Grub isn't a racist bootloader.
>
> Grub is a real piece of sh*t bootload that will totally destroy any and
> all Windows bootloaders. And when you delete linux, (which 99.99% of all
> those who try linux eventually end up doing) you have to make sure you
> manually remove all traces of grub (where do they get those stupid names
> from any way?) before deleting linux or else you cannot repair Vista bcd
> downloader using the repair option from the Vista DVD. It won't work!
> Best to load linix on a completely separate HDD with all of the other HDD
> unplugged. Then you can plug them in after the install and use the BIOS or
> your keyboard (F8 on some of mine) to load whichever OS you want.
>
> BTW, which "productivity application" won't run on Vista x64?
>
>>
>> Best of all worlds.
>>
>> Now for Frank, who will telly ou the real truth....
>
> I see you're once again passing out info that is meant to destroy Windows
> for unsuspecting users.
> Shame on you...LOL!
> Frank

http://support.microsoft.com/kb/919529

Read the above from your masters. The same FUD you spew about Linux happens
with dual booting XP with Vista. Say you had Vista OEM and XP --- Vista
already loaded. Once XP is installed the Vista bootloader is pooched. If
you get the Vista bootloader dual booting XP and Vista, then later decide to
stay XP and wipe Vista allocating the space to XP, you pooched your
bootloader.

That is one of the reasons I like Grub, it puts it in a separate partition,
and just leave that partition alone and it works. If you need to edit, boot
any Linux Live CD, mount and edit it. Or if you want to remove it, just run
the Vista boot manager and rewrite the boot tracks before removing grub.
Ideally testing it first.

I could be wrong, XP (32bit) bootloader does not load Vista x64.

Any time you are into booting more than 1 OS, you need to understand the
boot strap process(es). And Grub is plain superior in multi-boot
situations.

And did I detect that Frankie, you are not using Vista exclusively and dual
booting? Are you a closet user of XP or Linux?

Hahahahahahahahaha.

"Bob Campbell" <bob@bob.bob> wrote in message
news:RoWdnTmDat9d1ZbVnZ2dnUVZ_vyinZ2d@supernews.co m...
> "John Smith" <someone@microsoft.com> wrote in message
> news:8ZWdnZ7HmKOEJ5fVnZ2dnUVZ_hmtnZ2d@comcast.com. ..
>> After I get the 32 bit OS, I will figure out how to install it, and use
>> it. I surmise I will have to have some dual boot option - boot the 32 bit
>> OS whenever I telework, the 64 bit OS the rest of the time. I only
>> telework once a week so I will be using the VPN client about 15% of the
>> time.
>
> All you have to do is partition your disk. You can do this right in
> Vista - Control Panel, Computer Management, Disk Management. Right
> click on the disk under the blue line and select Shrink Volume. Shrink
> it down by whatever amount you want, but create enough free space to hold
> Vista 32 and whatever apps you need. This will leave empty space with a
> black line on top. Right click in this space and choose Create new
> volume. Format it and name it Vista32.
>
> Now just boot the Vista 32 DVD and install it on the new partition you
> just created. The dual boot will be setup automatically with your
> existing Vista 64.

Thanks a lot, Bob. I really appreciate your responses.

My simple question seemed to have generated way too much venom from some of
the other responders.

"Tom Lake" <toml_12953@hotmail.com> wrote in message
news:C0ABC9DC-E8A3-474F-9F7A-5E9A9B8FCF0C@microsoft.com...
>
> "Earle Horton" <earleh_nospam_@live.com> wrote in message
> news:18614838-A179-4746-86E3-41AF0DD27BBE@microsoft.com...
>
>>> Dzomlija, do you have a recommendation as to how to determine whether
>>> VPN client uses it's own
>>> communication stack?
>>>
>> Ask the vendor if it has been tested in Vista x64. If it hasn't been
>> tested, it doesn't work.
>
> I hope you're being facetious! Many companies don't have the resources to
> thoroughly test their products on every platform.

The company in question is Cisco.

I would be surprised if Cisco didn't have the resources to test their
products on current-release Windows versions.

It would be a rather bad sign for their shareholders, I would think.

I would have to add that whether it's been tested or not does not determine
whether it works or not. Testing reveals, it does not change.

> I run many 32-bit software
> packages which the vendor hasn't tested but which run perfectly fine in
> Vista-64.

Do they involve drivers? That is a significant qualifier.

Some companies will test to determine whether things work, and then if there
are significant problems will look at the market size and decide whether to
devote development and QA funds to the task. If the market isn't there,
development isn't undertaken and the "not supported" tag is applied.

In other words, it's proabably been tested, it doesn't work, and they don't
think it's worth the expense to fix it.

In any case, the OP needs to look this up at the Cisco site; that's where
the information is. And if his employer is requiring him to work at home
as well as the office, they should be providing him with the tools to do so.

A quick Google of 'cisco VPN client Vista" shows that some Cisco VPN clients
are not supported on Vista64, but one is. As to whether that one will work
with the employer's Cisco hardware, that's a matter for discussion with the
employer's IT staff.

http://www.cisco.com/en/US/products/...c2dbe.shtml#OS
==============
Q. Does Cisco provide a VPN Client for Windows Vista?


A. At the time of writing (June 2007) Version 5 of the VPN Client is
available for 32-bit Windows Vista. Support for 64-bit Windows Vista is not
available at this time. This client and release notes can be obtained from
the Software Center (registered customers only) .

Note: Cisco VPN Client is only supported on Windows Vista clean install.
It means that an upgrade of Windows of any OS to Windows Vista is not
supported with the VPN Client Software of this Vista. You must freshly
install the Windows Vista and try to install the Vista VPN Client software.

Note: If you do not have a valid service contract associated with your
Cisco.com profile you cannot log in and download the VPN Client software.
See Download VPN Client Software for more information.

Tip: The Cisco AnyConnect VPN Client is now available for the Windows
Operating Systems, which includes Vista 32 and 64-bit. The AnyConnect client
supports SSL and DTLS. It does not support IPSec at this time. Additionally,
AnyConnect is available only for use with a Cisco Adaptive Security
Appliance that runs version 8.0(2) or later. The client can also be used in
weblaunch mode with IOS appliances running version 12.4(15)T. VPN 3000 is
not supported.

The Cisco AnyConnect VPN Client and ASA 8.0 can be obtained from the
Software Center (registered customers only) . Refer to the Cisco AnyConnect
VPN Client Release Notes for more information on the AnyConnect Client.
Refer to the Cisco ASA 5500 Series Adaptive Security Appliances Release
Notes for more information on ASA 8.0.

Note: If you do not have a valid service contract associated with your
Cisco.com profile you cannot log in and download the AnyConnect VPN Client
or ASA software. See Download VPN Client Software for more information.
=============


HTH
-pk

>
> Tom Lake

"Dzomlija" <Dzomlija.382nl0@no-mx.forums.net> wrote in message
newszomlija.382nl0@no-mx.forums.net...
>
> John Smith;687234 Wrote:
>> In order to access my office network from home I am required to use a
>> company-supplied VPN client. The Cisco VPN client is for Windows 2000,
>> XP
>> and Vista - 32bit only.
>>
>> My home PC runs on 64 bit Vista Home Premium.
>>
>> Is it possible to run the PC is "32 bit mode" in order to get around
>> the
>> application requirement?
>>
>> Thanks in advance.
>
> You shouldn't have a problem using the 32-Bit VPN client on 64-Bit
> Windows which runs 32-Bit software as well as (if not better than) the
> 32-Bit versions of Windows.
>
> The one issue that you may encounter is if the VPN client uses 32-Bit
> device drivers for communication, in which case you're out of luck. One
> of the design features of Vista x64 is that you cannot under any
> circumstances use 32-Bit drivers.
>
> What you need to assess is whether or not the VPN client uses it's own
> communication stack, or if it uses the Windows facilities for
> communication. If it uses the Windows networking protocols, then chances
> are very good that it will work on Vista x64.
>
>
> --
> Dzomlija

Sorry about the date problem on the original post.

Dzomlija, do you have a recommendation as to how to determine whether VPN
client uses it's own
communication stack?