World: r3wp

Anyone seen this error before which has been reported to me


* Script Error: External process failed: %1 is not a valid Win32 
applic
ation.
 
** Near: launch "webserver"
view center-face loginlo
** Press enter to quit...

where "webserver" is just the argument for the 'launch command.

I can't tell you when the update SDKs will be released, only that 
the current SDK key will work with the new ones, no additional charge.

This is great news, Cindy. Thanks for assuring that.

Thanks!

thanks

I recall that someone was working on accessing the windows video 
api using rebol library access. Anybody knows ? thxs

Cyphre

thanks

SDK SDK SDK SDK (everybody) SDK SDK SDK SDK.... (to the tune of Queen's 
"We Will Rock You")

Still waiting for the new 1.3 version too.

.

:-)

I wish..I wish..I wish..(clack clack clack)....like Alice in Wonderland...

I have a problem, if I in a DOS-prompt under windows try to run a 
REBOL program built with REBOL/SDK into a .exe file, and the program 
is not in current directory, but has to be found along the PATH. 
I get the error
Program error: invalid encapsulated data


I've tried under Windows2000 and WinXP. Can others confirm this error? 
(Just make a simple REBOL-script with e.g. a print and try it.)

The problem (bug) can also be verified with altme.exe. Just setup 
path in the DOS-prompt to where, altme is located, and type: altme

I think REBOL needs a full path to itself.

It works, if you place yourself in the same directory as the .exe 
file and don't give full path. It also works, if you place yourself 
anywhere and give full or relative path. As I see it, the error is 
only, if you're not in the same directory as the .exe file, and the 
system finds it along the PATH environment variable. Maybe I should 
report it in RAMBO!?

you can report it, but i'm not completely sure it can be fixed.

From the builds page: "A Beta test version of the SDK with the 1.3.1 
fixes and changes is now available for current SDK developers. Contact 
REBOL via feedback or email Cindy if you would like to try it."

and it says its for win32

Geez, why  not just post it !!

(because of the source it contains?)

what about the exes ?

(but you need sources to have it complete, don't you?)

Hmm.  Yes, I guess so!

I stand corrected.

A Beta test version of the SDK with the 1.3.1 fixes and changes is 
now available for current SDK developers. Contact REBOL via feedback 
or email Cindy if you would like to try it.

I have recently started testing with Rebol/View 1.3, and decided 
to

purchase Rebol/SDK.  I have a function in one of my scripts that 
was
working in View during testing, but as soon I start using the SDK
binaries it no longer... um... functions.


In the function, I am trying to set a value in an array using an 
index
variable.

In view, I could do:
   values/:index: value
But in the SDK, I get:
   ** Syntax Error: Invalid word -- :index:

Again, any help would be appreciated.

Thank you,
robert w. dumond

from the mail list

bata-sdk. also noted on the ML IIRC.

But the subdirectory is not mentioned by sunanda, and not linked 
public.

plis help

kernel-lib: load/library %kernel32.dll
WriteFile: make routine! [
        hFile                   [integer!]
        lpBuffer                [integer!]
        nNumberOfBytesToWrite   [integer!]
        lpNumberOfBytesWritten  [integer!]
        lpOverlapped            [integer!]
        return:                 [integer!]
 
    ] kernel-lib "WriteFile"

it does not actit

how do to write in rebolu this ?

[DllImportAttribute("kernel32", SetLastError=true)]


        private static extern IntPtr CreateFile(string _lpFileName, 
                                           uint _dwDesiredAccess,

                                                 uint _dwShareMode,

                                        uint _lpSecurityAttributes, 

                                       uint _dwCreationDisposition,

                                        uint _dwFlagsAndAttributes, 

                                              uint _hTemplateFile);

        [DllImportAttribute("kernel32", SetLastError=true)]

        private static extern bool WriteFile(IntPtr _hFile, void* _lpBuffer, 
        uint _nNumberOfBytesToWrite, uint* _lpNumberOfBytesWritten, uint 
        _lpOverlapped);

        [DllImportAttribute("kernel32", SetLastError=true)]
        private static extern bool CloseHandle(IntPtr _hObject);

        [DllImportAttribute("kernel32", SetLastError=true)]

        private static extern bool DeviceIoControl(IntPtr _hDevice, uint 
        _dwIoControlCode, void* _lpInBuffer, uint _nInBufferSize, void* lpOutBuffer, 
        uint _nOutBufferSize, uint* _lpBytesReturned, uint _lpOverlapped);

unsiged integers can safely be casted to integers, you sould know 
that some dll's wont work just because the need special arguments 
like pointers to certain data etc... nay whay why do you need to 
write a file using windows API can't you use rebol ?

btw lpOverlapped  is a pointer to a structure OVELAPPED you can pass 
a structure pointer from rebol using, lpOverlapped [struct! [(OVERLAPPED)]]
the scructure looks like this 
OVERLAPPED: make struct! [
	Internal		[integer!]
	InternalHigh		[integer!]
	Offset			[integer!]
	OffsetHigh		[integer!]
	hEvent			[integer!]
] none
again this still may not work ....

how small a Rebol executable can you build with the SDK? if you take 
away everything? just curious...

300k from memory.

thanks

Base is a little smaller (~250K), but that's close enough. If you 
need GUI stuff, it will be around ~550K minimum (using rebface) or 
~650K using all of view and VID..

If space is an issue, you can save a lot of space by removing protocols 
that aren't required. I got a few with full VID based but with only 
http protocol supported.. 506kb, 

I'm sure I could drop another 80-100 if I switched to using rebface.

Good place to discuss a remote encapping service? The idea would 
be for RT to provide a service that would allow you to encap source 
code without the SDK. RT encaps your files and provides you with 
an executable that works for 5 minutes. If you pay a fee (5$?), you'll 
get no time limitation.


This could be for people who can't afford the SDK, want to use the 
encap facility to see what it's all about or simply only need to 
encap a single application.

an encap service as been discussed many times in the past. there 
are a number of problems in doing it.

there could be further limitations, such as only allow up to 50 kB 
of source code, or only to a specific platform.

ok...

the problem is mainly that the process cannot be automated, because 
anyone going to encap a submission must verify that it complies with 
the encap licensing terms.

which basically would mean a rewrite of /encap?

I think it would mean rewrite of licensing.