Menu
▾
▴
[Oorexx-bugs] [ oorexx-Bugs-2850191 ] every rexx crahes under vista, samples too
|
From: SourceForge.net <no...@so...> - 2009-09-04 22:22:58
|
Bugs item #2850191, was opened at 2009-09-03 12:18 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2850191&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interpreter Group: v4.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: bugstumbler (bugstumbler) Assigned to: Nobody/Anonymous (nobody) Summary: every rexx crahes under vista, samples too Initial Comment: event log entry: Fehlerhafte Anwendung rexx.exe, Version 4.0.0.5088, Zeitstempel 0x4a86c84a, fehlerhaftes Modul rexx.dll, Version 4.0.0.5088, Zeitstempel 0x4a86c841, Ausnahmecode 0xc0000005, Fehleroffset 0x0001a302, Prozess-ID 0x1418, Anwendungsstartzeit 01ca2cc71517b630. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2009-09-04 15:22 Message: We do not have a cleanup script, or an installation health checker. 0xc0000005 is simply the code for a memory access violation and the address of the violation, 0x0001a302 is meaningless to me, and anyone else. Since no one has reported anything remotely close to this, and there is not enough information from you to even speculate on what the problem is, you are mostly likely going to have to solve this yourself. If you actually had Open Object Rexx 2.1.3 installed as I think you are suggesting, then this is what I would do: * Use the uninstall of ooRexx 4.0.0 to completely remove ooRexx. Check that the installation directory is empty / and or deleted. * Use task manager to determine that there is no rxapi or rexx process running. If there is, kill them. * Use the administrator's Services tool to check for a service with the name of rxapi. If there is one listed, then your problem is pretty much solved. a.) If the rxapi service is listed, open up the properties for the rxapi service and make note of the path to the executable. Then use the properties page to stop the process, then set the start up type of rxapi to 'disabled.' b.) Go to the directory listed as the path to the excutable and delete it and everything in it. * Use a program to search your entire hard disk (or disks) and find every instance of rexx* and every instance rxapi*. Delete evey one you find, and probably the files with them. * You can search the registry for old IBM Object Rexx entries and delete them. The string "Object Rexx" makes a good search term. Alternatively, you could try and find an inexpensieve "registry cleaner" and try it. I make no recommendations here, every one is on their own when it comes to the registry. Do what you're comfortable with. If the above doesn't help. Then you will need to supply us with a lot more information. Exactly what options are you using to install with and where are you installing to? Exactly what steps you take to produce a crash. Describe exactly what you mean by crashes. Add screen shots of exactly what happens when rexx crashes. ---------------------------------------------------------------------- Comment By: bugstumbler (bugstumbler) Date: 2009-09-03 21:39 Message: >> You either have a bad install, or something else is going on. Try completely >> uninstalling ooRexx, ... I did this twice. Perhaps there are remaining artefacts from a former 2.1.3 installation. Do you have a cleanup-script or a short documentation, where and what 2,1,3 entries have to be deleted in registry ? Alternatively do you provide a REXX installation health checker ? Alternatively you take the info "eventcode 0xc0000005, Offset 0x0001a302, rexx.dll" to a programmer and let him roughly tell you, what rexx.dll intends to do before it crashes. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2009-09-03 13:28 Message: All the samples work fine for me on both Vista 32-bit and 64-bit with the release 4.0.0: C:\Program Files\ooRexx\samples>drives ┌─────┬────────────────┬────────────────┬──────────────┬────────┬──────────┐ │Drive│ Free │ Total │ Label │Location│Filesystem│ ├─────┼────────────────┼────────────────┼──────────────┼────────┼──────────┤ │ C: │ 63.413.338.112 │ 96.737.423.360 │ │ local │ NTFS │ │ D: │ │ │ CD-ROM │ │ │ │ E: │ 68.477.599.744 │100.644.417.536 │ │ local │ NTFS │ │ F: │ 81.014.681.600 │122.683.387.904 │ │ local │ NTFS │ │ J: │ │ │ CD-ROM │ │ │ │ P: │223.398.764.544 │262.143.995.904 │ TempBackUp │ local │ NTFS │ │ Z: │ 3.239.276.544 │ 26.213.933.056 │ Blackfoot │ remote │ NTFS │ └─────┴────────────────┴────────────────┴──────────────┴────────┴──────────┘ Operating System Version : WindowsNT 6.00 Bootdrive : C: Used drives : C: D: E: F: J: P: Z: Local drives : C: D: E: F: P: RAM drives : No RAM Drives Remote drives : Z: Drive letters not used : G: H: I: K: L: M: N: O: Q: R: S: T: U: V: W: X: Y: C:\Program Files\ooRexx\samples> C:\Program Files\ooRexx\samples>rexx -v Open Object Rexx Version 4.0.0 Build date: Aug 15 2009 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html C:\Program Files\ooRexx\samples> I know a lot of other people are using ooRexx on Vista, without crashing. You either have a bad install, or something else is going on. Try completely uninstalling ooRexx, make sure you have no other Rexx installed, and then re-install. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2850191&group_id=119701 |