Windows 7 and Wildfire 3.0 1

[Albion]

Has anyone had any luck installing Wildfire 2.0 and 3.0 in Windows 7? We just purchased a new Windows 7 machine and unfortunately our customers have not upgraded from Wildfire 2.0 as of yet.

Thanks

 

[looslib]

There is no technical reason it should not work.

The key with a new OS is the graphic drivers.
As long as you are NOT running the home version of Windows, you should be OK.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[Albion]

Unfortunately I can't get setup.exe to run no matter what compatibility mode I try. I failed to mention that this is a 64 bit version of Win7 Pro.

Thanks.

 

[dgallup]

You can install either the 32 or 64 bit version of Pro/E on a 64 bit OS. Be aware however, that neither WF2 or WF3 is officially supported on Win7. Most people buying new machines during the Vista rein of terror wiped the disk & installed XP. That may be your best bet but make sure of driver availability first.

 

[PeterStock]

You might try to run Pro in XP compatible mode.

Peter Stockhausen
Senior Design Analyst (Checker)
Infotech Aerospace Services

http://www.infotechpr.net

 

[jstiles]

I just went thru an installation of WF 3.0 in both the XP Mode/Virtual PC and VMware Workstation 7 environments. Virtual PC limits the emulated video card to 16MB and VMware goes to 256MB. Needless to say the Virtual PC was a non-starter. The VMware environment worked well for small/light-weight models but became graphically challenged when opening larger (100+ part) assemblies and drawings were terrible. Much of the text became garbled and shown in locations that it was not actually in. My next step is to set up my Win 7 box as a dual boot with XP Pro 64-bit as the 2nd option. Fortunately we're migrating to SolidWorks so the dual boot issue will eventually go away. Would be nice if there was a patch file to make WF 3.0 work in Win 7.

 

[looslib]

I doubt any of the problems with WF3 and Windows7 could be fixed with a patch from PTC. Most of the issues revolve around drivers and MS security that is in W7. Only MS understands what they have impossed on those of us who need advanced access to the OS.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[jstiles]

With some help from a good friend of mine, I was able to get WF 3 32-bit to run in Win7. It's so rediculously easy you wonder why you didn't think of it yourself. Just copy your load point directory to a DVD, flashdrive, or network drive. Once you hav Win7 updated, just copy the load point back to your PC and BINGO! you're up and running. I can't believe that it works but it does. I've been running this way for a couple of weeks and using intralink and there have been no issues that I have seen.

Now if I could just figure out how to get 64-bit to run, I'd be truly happy. It won't even start up.

 

[ingallspw]

jstiles...

At first I didn't know exactly what you meant by "load point" but this explained it.

http://www.ptc.com/olm/ist1071/ist_faq.htm#6z

Second, I am trying to fully understand your solution. What I hear you saying is to just copy the entire folder containing all the PTC software installed on an XP machine to the new W7 PC?

Are there no registry files, user folders, common files, etc that need to come with it?

And if jstiles is correct and this works, it makes me wonder why PTC wouldn't push out a solution. I know that looslib has a point about Windows 7 but if this works, that is a non issue.

I just don't get PTC. I have Siemens NX installed, Solid works installed, heck even crappy old AutoCAD installed... no problems there but with ProE the self proclaimed industry leader... Please see the attached link for further explanation:

http://www.qwizx.com/gssfx/usa/tpirhorns.wav

 

[dgallup]

Pro/E does not need any registry entries to run. If fact, I don't install it on our workstations at all. I just install it on a server and put a shortcut on the users desktop. The only other thing that is needed is an addition to the PATH environment variable to the loadpoint\bin directory. But even this is only necessary if you want to run shell commands like purge outside of Pro/E.

 

[jstiles]

ingallspw & dgallup are correct in their assumptions about copying the files/folders, no registry entries, etc. and information about environment variables. Sorry I wasn't more clear and complete.

 

[ingallspw]

Sweet! It works! You da man!

(Now why can't PTC figure this out?)

Thanks ALL!

 

[ingallspw]

"Wow" in fact...

It seems to work better in Windows 7!

It loads almost instantly compared to what i am used to! Great job guys!

 

[dgallup]

PTC's setup.exe script tries to figure out what OS it is running in and obviously doesn't know what to do with windoze 7 as it didn't exist when the script was written.

 

[bsekle]

Hi, I'm trying to install version 5.0 on Windows 7. I first installed it on Windows XP and the program files created were proeWildfire 5.0 and PTC. I copied those folders onto an external hard drive and then copied them from the external hard drive into my program folder in Windows 7. I tried to run the software and got the message "No write access to C:\Program Files\proeWildfire 5.0\bin\". In light of what was said about getting ProE to work in Windows 7, does anyone know what I'm doing wrong?

Thanks, your help would be greatly appreciated.

 

[Albion]

WF 5.0 should install natively in Windows 7. Just make sure you have the right version of ProE. I.E. if you're running a 64bit machine with a 64bit Windows 7, then you should be installing the 64bit version of ProE.

 

[bsekle]

I'm running a 32 bit machine with a 32 bit Windows 7 and a 32 bit version of ProE.