Upgraded to 64-Bit XP can't open existing files

N/A

We upgraded our work stations to 64 bit cpu's and windows xp professional 64. Now
when we try to open any files created by the 32 bit machines we get the attached
error. We have tried both V19 and V20. Ant suggestions?
6 REPLIES

Re: Upgraded to 64-Bit XP can't open existing files

N/A
SE2D is 32 bit code, so are you running it in WOW64 (32 bit emulation mode)?
--
PellaKen
http://grundey.blogspot.com
"Andy Bancroft" wrote in message
news:475d9e42$1@bbsnotes.ugs.com...
>
> We upgraded our work stations to 64 bit cpu's and windows xp professional
> 64. Now
> when we try to open any files created by the 32 bit machines we get the
> attached
> error. We have tried both V19 and V20. Ant suggestions?
>


Re: Upgraded to 64-Bit XP can't open existing files

N/A

Not sure. How can you tell?

"Ken Grundey" wrote:
>SE2D is 32 bit code, so are you running it in WOW64 (32 bit emulation mode)?
>
>--
>PellaKen
>http://grundey.blogspot.com
>"Andy Bancroft" wrote in message
>news:475d9e42$1@bbsnotes.ugs.com...
>>
>> We upgraded our work stations to 64 bit cpu's and windows xp professional

>
>> 64. Now
>> when we try to open any files created by the 32 bit machines we get the

>
>> attached
>> error. We have tried both V19 and V20. Ant suggestions?
>>

>
>

Re: Upgraded to 64-Bit XP can't open existing files

N/A
Don't know. I just know that it cannot be run natively as it is not a 64
bit app and has to run in the emulator. Not sure if it is automatic or you
have to specify it.
--
PellaKen
http://grundey.blogspot.com
"Andy Bancroft" wrote in message
news:475dba10$1@bbsnotes.ugs.com...
>
> Not sure. How can you tell?
>
>
> "Ken Grundey" wrote:
>>SE2D is 32 bit code, so are you running it in WOW64 (32 bit emulation
>>mode)?
>>
>>--
>>PellaKen
>>http://grundey.blogspot.com
>>"Andy Bancroft" wrote in message
>>news:475d9e42$1@bbsnotes.ugs.com...
>>>
>>> We upgraded our work stations to 64 bit cpu's and windows xp
>>> professional

>>
>>> 64. Now
>>> when we try to open any files created by the 32 bit machines we get the

>>
>>> attached
>>> error. We have tried both V19 and V20. Ant suggestions?
>>>

>>
>>
>

Re: Upgraded to 64-Bit XP can't open existing files

N/A
It sounds like a bad install to me. I would uninstall Solid Edge, clean the
registry (ask other newsgroup folks how to do this) and reinstall and retry.
PS> Why in the world are you running a 64 bit OS if all you're doing is 2D
drafting?
DS

"Andy Bancroft" wrote in message
news:475dba10$1@bbsnotes.ugs.com...
>
> Not sure. How can you tell?
>
>
> "Ken Grundey" wrote:
>>SE2D is 32 bit code, so are you running it in WOW64 (32 bit emulation
>>mode)?
>>
>>--
>>PellaKen
>>http://grundey.blogspot.com
>>"Andy Bancroft" wrote in message
>>news:475d9e42$1@bbsnotes.ugs.com...
>>>
>>> We upgraded our work stations to 64 bit cpu's and windows xp
>>> professional

>>
>>> 64. Now
>>> when we try to open any files created by the 32 bit machines we get the

>>
>>> attached
>>> error. We have tried both V19 and V20. Ant suggestions?
>>>

>>
>>
>

Re: Upgraded to 64-Bit XP can't open existing files

N/A

This is happening on multiple machines/installs.
Our workstations also run UGNX5 and were upgraded for this.
Solid Edge free2d will start a new file with out a problem.
It is just the files created by the 32 bit machines that we are unable to open.
Unfortunatley this includes all of our backgrounds, symbol files, existing drawings,
etc.

"Dan Staples" wrote:
>It sounds like a bad install to me. I would uninstall Solid Edge, clean the
>
>registry (ask other newsgroup folks how to do this) and reinstall and retry.
>
>PS> Why in the world are you running a 64 bit OS if all you're doing is 2D
>
>drafting?
>
>DS
>
>
>"Andy Bancroft" wrote in message
>news:475dba10$1@bbsnotes.ugs.com...
>>
>> Not sure. How can you tell?
>>
>>
>> "Ken Grundey" wrote:
>>>SE2D is 32 bit code, so are you running it in WOW64 (32 bit emulation
>>>mode)?
>>>
>>>--
>>>PellaKen
>>>http://grundey.blogspot.com
>>>"Andy Bancroft" wrote in message
>>>news:475d9e42$1@bbsnotes.ugs.com...
>>>>
>>>> We upgraded our work stations to 64 bit cpu's and windows xp
>>>> professional
>>>
>>>> 64. Now
>>>> when we try to open any files created by the 32 bit machines we get the
>>>
>>>> attached
>>>> error. We have tried both V19 and V20. Ant suggestions?
>>>>
>>>
>>>

>>
>
>

Re: Upgraded to 64-Bit XP can't open existing files

N/A

Problem solved by installing 2.0 .NET framwork (x64) from microsoft.
Andy
"Andy Bancroft" wrote:
>
>This is happening on multiple machines/installs.
>
>Our workstations also run UGNX5 and were upgraded for this.
>
>Solid Edge free2d will start a new file with out a problem.
>
>It is just the files created by the 32 bit machines that we are unable to
>open.
> Unfortunatley this includes all of our backgrounds, symbol files, existing
>drawings,
>etc.
>
>
>
>"Dan Staples" wrote:
>>It sounds like a bad install to me. I would uninstall Solid Edge, clean the
>>
>>registry (ask other newsgroup folks how to do this) and reinstall and retry.
>>
>>PS> Why in the world are you running a 64 bit OS if all you're doing is 2D
>>
>>drafting?
>>
>>DS
>>
>>
>>"Andy Bancroft" wrote in message
>>news:475dba10$1@bbsnotes.ugs.com...
>>>
>>> Not sure. How can you tell?
>>>
>>>
>>> "Ken Grundey" wrote:
>>>>SE2D is 32 bit code, so are you running it in WOW64 (32 bit emulation
>>>>mode)?
>>>>
>>>>--
>>>>PellaKen
>>>>http://grundey.blogspot.com
>>>>"Andy Bancroft" wrote in message
>>>>news:475d9e42$1@bbsnotes.ugs.com...
>>>>>
>>>>> We upgraded our work stations to 64 bit cpu's and windows xp
>>>>> professional
>>>>
>>>>> 64. Now
>>>>> when we try to open any files created by the 32 bit machines we get the
>>>>
>>>>> attached
>>>>> error. We have tried both V19 and V20. Ant suggestions?
>>>>>
>>>>
>>>>
>>>

>>
>>
>