Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

STEP5 COM crashes

Created by: MIMR at: 6/19/2014 10:55 AM (3 Replies)

Rating (0)

Thanks 1

4 Entries

6/19/2014 10:55 AM	Rate (0)
MIMR Advanced Member Joined: 9/8/2008 Last visit: 11/4/2024 Posts: 23 Rating: (0)	Hello, I cannot start any COM (COM155H, COMNCM,...) from STEP5. I have moved STEP5 to newer PC with WXP SP3. STEP5 itself works OK, but after starting of any COM, STEP5 window disappears. I have tried it with several PCs, always with WXP SP3 and STEP5 V7.1, 7.2 or 7.23 and result is, that on PC older than approximately 5 years it works OK regardless of STEP5 version, on newer PCs not. Recomendations about /onecpu and no eprom driver I accepted already. Is there any solution? Thanks to all.

Suggestion To thank Quote Answer

6/19/2014 11:28 AM	Rate (0)
Navnag Platinum Expert Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308)	MIMR Hello, I cannot start any COM (COM155H, COMNCM,...) from STEP5. I have moved STEP5 to newer PC with WXP SP3. STEP5 itself works OK, but after starting of any COM, STEP5 window disappears. I have tried it with several PCs, always with WXP SP3 and STEP5 V7.1, 7.2 or 7.23 and result is, that on PC older than approximately 5 years it works OK regardless of STEP5 version, on newer PCs not. Recomendations about /onecpu and no eprom driver I accepted already. Is there any solution? Thanks to all. I am using STEP7 V7.23 on a Laptop with Windows-XP SP3 and have no problem opening the COM Packages. So I would suggest to check if your STEP5 Installation files are corrupted. Try with a different setup CD. Alternatively you can install STEP5 in a Virtual Machine using a Virtualisation software like Vmware. Here you can select the OS Type to be installed as well as CPU properties. I have STEP5 installed in a Vmware Workstation based Virtual Machine running Win-XP+SP2 and it works just fine. Hope this helps Cheers Navnag
	There is no such thing as the last bug in a program There are no stubborn bugs, There are only stubborn Debuggers.
Suggestion To thank Quote Answer

6/19/2014 2:35 PM	Rate (0)
MIMR Advanced Member Joined: 9/8/2008 Last visit: 11/4/2024 Posts: 23 Rating: (0)	Dear Navnag, many thanks for reaction, I can add now more questions: I have found the reason now. Problem is in S5KXS06X.COM, which checks the interrupt vector E2. In PG, there is the real interrupt vector, in "old" PC's there is 0000:0000, which bothare OK for S5KXS06X.COM. In "new" PC'sI see there values0000:0001 or 46A9:0001 or simillar, whichresults to immediate crash (check of word address xxxx:FFFF). I have deleted (patched with NOP's) this E2-interrupt check from S5KXS06X.COM and itseems to be oknow. May is possible to write simple resident program, which maintain E2 vector, to. But- is there any "standard-Siemens"solution? Best regards, Mrk.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Navnag

6/19/2014 2:52 PM	Rate (0)
Navnag Platinum Expert Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308)	MIMR But- is there any "standard-Siemens"solution? I don't think siemens is going to release any fresh patches / updates for STEP5. This stopped long ago. So the best solution seems to be either a Dual Boot Machine e,g, : SIMATIC Field PG M4: Pre-Loaded Software "V12.0.1.0"; Dual-Boot (XP/Windows 7); CCC; USB 3.0 SATA Adapter or use a Virtual Machine as suggested previously. Cheers Navnag.
	There is no such thing as the last bug in a program There are no stubborn bugs, There are only stubborn Debuggers.
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on