HellBent
Automotive
- Sep 29, 2002
- 130
Hey all...long time no post 
Ran into a problem a couple times over the last few weeks that wasn't a big deal until it cost me a day's worth of work so I figured I'd post about it because although the topic had been somewhat addressed a couple times on a few different sites, none of the given answers turned out to be the solution to our problem.
So I'd open a part file...do a bunch of work....save the file. Go to open the file back up later and get the following warnings/errors:
OSM_RE001
OSM_AL080
OSM_VE004
OSM_AL035
OSM_AL115
0SM_AL034
0SM_AL033
My machine has v5r18 and v5r19 installed on it but I work exclusively in r18. With none of our various r18 environments able to open the file, for shits and grins I decided to try to open it in 19. Whalla! (as good a spelling for that I could come up with) It opened in 19 no problem. I opened up the part file in Wordpad and about 40 lines down or so the part files will tell you what version they were created in. Somehow my file had been saved as a r19 file. How? Good question. Took me a little bit to re-trace my steps and figure it out. If you're on a machine with multiple versions Windows will automatically associate the last version you installed to the file extension. Meaning...if you installed 19 last and double-click on a .catpart in windows explorer...it's going to open in 19 if you don't already have a different version open and running. If you have 18 open and double-click a file name it will try to bring it into the session that is already up and running. But if you don't have a session up it's going to run whatever version was installed last..which on my machine was 19. The installation programs automatically configure the Windows file associations to run with whatever executable you're installing.
The machines at our company are all configured identically, which is the norm at most large companies, but I don't personally work on any jobs that use 19 so the thought of it even being on my machine never even came to mind until I came across this problem with my files. There's really no simple fix other than just realizing that if you double-click the file to open it there is a chance it's going to open up into the unintended version of Catia.
'This is the case for all software, dummy!' you might say. And you'd be correct. But with so many different manufacturers using Catia and each of them using different environments and versions the problem is probably a lot more common with Catia than with other cad packages. Most other packages also make it pretty obvious what version you're firing up, Catia doesn't....r19 looks exactly like r18 with no splash screens telling you what you're actually firing up. You can setup custom backsplashes if you want...this could help a lot. I'm a pretty good gambler and I'm betting I'm not the only one who lost a bunch of work to this simple mistake before I figured it out. Until today I would have just chalked it up to another 'stupid Catia problem'. Turns out it was just another 'stupid user problem' and maybe this post will help out some of the other idiots out there
Take it easy.
Ran into a problem a couple times over the last few weeks that wasn't a big deal until it cost me a day's worth of work so I figured I'd post about it because although the topic had been somewhat addressed a couple times on a few different sites, none of the given answers turned out to be the solution to our problem.
So I'd open a part file...do a bunch of work....save the file. Go to open the file back up later and get the following warnings/errors:
OSM_RE001
OSM_AL080
OSM_VE004
OSM_AL035
OSM_AL115
0SM_AL034
0SM_AL033
My machine has v5r18 and v5r19 installed on it but I work exclusively in r18. With none of our various r18 environments able to open the file, for shits and grins I decided to try to open it in 19. Whalla! (as good a spelling for that I could come up with) It opened in 19 no problem. I opened up the part file in Wordpad and about 40 lines down or so the part files will tell you what version they were created in. Somehow my file had been saved as a r19 file. How? Good question. Took me a little bit to re-trace my steps and figure it out. If you're on a machine with multiple versions Windows will automatically associate the last version you installed to the file extension. Meaning...if you installed 19 last and double-click on a .catpart in windows explorer...it's going to open in 19 if you don't already have a different version open and running. If you have 18 open and double-click a file name it will try to bring it into the session that is already up and running. But if you don't have a session up it's going to run whatever version was installed last..which on my machine was 19. The installation programs automatically configure the Windows file associations to run with whatever executable you're installing.
The machines at our company are all configured identically, which is the norm at most large companies, but I don't personally work on any jobs that use 19 so the thought of it even being on my machine never even came to mind until I came across this problem with my files. There's really no simple fix other than just realizing that if you double-click the file to open it there is a chance it's going to open up into the unintended version of Catia.
'This is the case for all software, dummy!' you might say. And you'd be correct. But with so many different manufacturers using Catia and each of them using different environments and versions the problem is probably a lot more common with Catia than with other cad packages. Most other packages also make it pretty obvious what version you're firing up, Catia doesn't....r19 looks exactly like r18 with no splash screens telling you what you're actually firing up. You can setup custom backsplashes if you want...this could help a lot. I'm a pretty good gambler and I'm betting I'm not the only one who lost a bunch of work to this simple mistake before I figured it out. Until today I would have just chalked it up to another 'stupid Catia problem'. Turns out it was just another 'stupid user problem' and maybe this post will help out some of the other idiots out there
Take it easy.
