programming tools for Windows applications development
  Home  |   SwiftForth Archive  |   SwiftX Archive  |

Re: bear of a problem

From: Roger Dube <rdube_at_entropylock.com>
Date: Tue, 18 Nov 2003 18:33:24 -0500

1. I try to execute my turnkey, which involves a popup window and a
selection that is then followed by a TCPIP send. On this one machine, I
mis-remembered the failure message: I actually get an ERROR popup with ||
and a choice of terminate or details ... details yields a WAIT_0 dialog:

WAIT_0

Registers Dstack Rstack

 EAX 00000000 00000000 00000000

 EBX 00000000 00000000 00000000

 ECX 00000000 00000000 00000000

 EDX 00000000 00000000 00000000

 ESI 00000000 00000000 00000000

 EDI 00000000 00000000 00000000

 EBP 00000000 00000000 00000000

 ESP 00000000 00000000 00000000

 EFL 00000000 002A0000 00000000

 EIP 00000000 00000003 2C000000

2. SF was used on "my" machine to compile the turnkey, and the turnkey
executable works fine on that and other machines... it is this new one that
worries me.

- Roger

----- Original Message -----
From: "Rick VanNorman" <rvn_at_forth.com>
To: <sftalk_at_forth.com>
Sent: Tuesday, November 18, 2003 6:11 PM
Subject: [sftalk] Re: bear of a problem

> 1. In what context do you see the "can't" message and exactly what does it
> say?
>
> 2. What are you executing when you get it? Are you trying to load sf.exe
> in order
> to compile the program, or have you already done a compilation and you're
> trying
> to run the resulting executable?
>
>
>
> On Tue, 18 Nov 2003 18:03:39 -0500, Roger Dube <rdube_at_entropylock.com>
> wrote:
>
> > I have a tough problem... I have been developing code which involves use
> > of winsock and tcpip "conversations" between two computers. Development
> > has gone well, and it works smoothly on several computers, all with XP
> > and Windows 2000.
> > But there is a brand new XP machine in the office on which the software
> > does not work at all - I get "can't open file" and related failures.
> >
> > I believe the file it needs is likely a Windows or system file, rather
> > than a DLL or other file that I have created, since those are all
> > present and available in the same folder that carries the turnkey. In
> > fact, I am able to rename some likely folders in the root drive of
> > machines that "work" and still be able to get the software operating,
> > since it carries along the DLLs it needs in its own folder.
> >
> > SO: how do I find out WHAT file is missing? I would guess that some use
> > of the debug mode might be in order here... but that means that I can't
> > just carry my turnkey and related files folder to the new machine... I
> > would need to install SF on the system, right?
> >
> > I know this is not a crisp question, nor can I supply code, since it is
> > too massive... but suggestions on how to tackle the basic problem of
> > ambiguous or uninformative error messages would be much appreciated.
> >
> ----------------------------------------------------------------------
> sftalk_at_forth.com The SwiftForth programming discussion email list
> To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
> For list command help, send subject "help" to sftalk-request_at_forth.com
> Message archives are located at http://www.forth.com/archive/sftalk
> ----------------------------------------------------------------------
> This list is a forum for SwiftForth users. For product support and bug
> reports, please send email to support_at_forth.com
> ----------------------------------------------------------------------
>

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
For list command help, send subject "help" to sftalk-request_at_forth.com
Message archives are located at http://www.forth.com/archive/sftalk
----------------------------------------------------------------------
This list is a forum for SwiftForth users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Tue Nov 18 2003 - 15:41:08 PST

This archive was generated by hypermail 2.2.0 : Tue Dec 02 2008 - 03:04:34 PST