Re: bear of a problem

You may have a permissions problem. XP can be very picky about file
access to program directories. Try the following redefinitions -
they'll report an error even if your main window is not yet created.
Load these early in your program.

-? \ Redefined test version
: OPEN-FILE ( c-addr u fam -- fileid ior )
   R-BUF THIRD THIRD R@ ZPLACE
   OPEN-FILE DUP ( error? )
   IF 0 ( No HWND ) R@ Z" File Open Error"
      MB_SYSTEMMODAL MB_ICONERROR OR MB_OK OR MessageBox DROP
   THEN R> DROP ;

-? \ Redefined test version
: CREATE-FILE ( c-addr u fam -- fileid ior )
   R-BUF THIRD THIRD R@ ZPLACE
   CREATE-FILE DUP ( error? )
   IF 0 ( No HWND ) R@ Z" File Create Error"
      MB_SYSTEMMODAL MB_ICONERROR OR MB_OK OR MessageBox DROP
   THEN R> DROP ;

Regards,

Mike

-----Original Message-----
From: sftalk-bounce_at_forth.com [mailto:sftalk-bounce_at_forth.com]On
Behalf
Of Roger Dube
Sent: Tuesday, November 18, 2003 3:04 PM
To: sftalk_at_forth.com
Subject: [sftalk] bear of a problem

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.

- Roger
----------------------------------------------------------------------
Dr. Roger Dube

RogerDube_at_datHQ.com
President/CEO
Digital Authentication Technologies, Inc.
http://www.datHQ.com/
TEL +1.561.392.7404
FAX +1.561.892.2474

PO Box 811564
Boca Raton, FL 33481-1564

----------------------------------------------------------------------
This E-mail message and any attachments have been scanned for viruses
and are believed to be free of any virus or other defect that might
affect any computer system into which it is received and opened.
However,
it is the responsibility of the recipient to ensure that it is virus
free
and no responsibility is accepted by Digital Authentication
Technologies,
Inc. for any loss or damage arising in any way from its use. This
email
message is for the sole use of the intended recipient(s) and may
contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message. Any views expressed in this message
are
those of the individual sender, except where the sender specifically
states them to be the views of Digital Authentication Technologies,
Inc.

----------------------------------------------------------------------
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 - 17:06:25 PST