----------------------------------------------------------------------- [2 hours on ICI280] [Yes! The intercomputer organization architecture is finnaly implented! It's no obscure function as it is part of what I originaly had in mind as part of this software, a key part in fact. It allows each node to find another that will be ready to do it's task in a fairly reliable manner. This way, functions do not require to know anything other of the destination than the fact that it's in the ICI network; they can be hardcoded to use 'foregin' function names without risking to lose any of the ICI's typical flexibility. The architecture is built to naturaly and effectively spread the tasks amongst the nodes according to overal (processing and network) speed, always assuring the fastest service. Hope you like it as much as I do.] [All functions are supposed to know the command: "Echo", followed by the source computer's name (supposed to be used in the reply to the Console) and any additional parameters. Such an echo request is confirmed with a "Please bounce" followed with the previously provided source computer's name and the function's name.] ----------------------------------------------------------------------- [] --- Hold: ----------------------------------------------------------------------- [2 hours on GUI4FTE130] ----------------------------------------------------------------------- [ICSADRLS.exe is placing the "FTE.rtn" in the dir it is running from. Problem could be fixed by using FileLoc.] [Day first, then month, please! (DD:MM:YYYY)] [If I browse to "C:\Program files" nothing will be returned by ICSADRLS.exe] ----------------------------------------------------------------------- Was: [n_nelson@dslextreme.com wrote: > Clicking on a filename and clicking on `Download' gets: > > Return_file=C:\Download\Jure\ici\FTE.rtn > FromName=Local > FromPath=C:\Programs\ICI\tcp\GUI4FTE121.zip > ToName= > ToPath=C:\Download\Jure\ici\GUI4FTE121.zip > Action=Copy > > Here it would be good to have the ToName, but for the time being it can > be avoided and assumed to be the local node name when not present. > The path names are correct here. I'll check, but this does not appear to be a problem from my end.] Now: [No problem with my version. What ICI nodes do you have registered in your Console's ICI cluster??] ----------------------------------------------------------------------- [15 minutes on GUI4FTE v122] [Some bugs fixed and: MSGBOX=Yes MSGBOX_Text=Message box text MSGBOX_Title=Message box title MSGBOX_Type=Number indicating message box type] ----------------------------------------------------------------------- [1 hour on GUI4FTE110] [1.3 hours on Console v277] [3 hours on GUI4FTE121] [Console v277 no longer suffers of the "early start" syndrome, which was a common bug in my programs. I now discovered any removed it. The problem was that before the Console loaded, it had to be using a special method to let it display the splash screen, which allas also allowed all the internal timers to take off, preforming startup operations that were only supposed to take place after loading was completed. Also some other bugs have been removed.] ----------------------------------------------------------------------- [2 hours on GUI4FTE] [Here is the GUI for FTE, it utilizes everything I know of. You will notice that the destination list ("node:...") includes all the nodes you have on your Console will automatical appear there on startup (because of FileLoc, you don't have to do anything more than run the program). I have introduced a "ICSA_FTE_Return" property for the FileLoc, which will look for a 'Return' file named "FTE.rtn", that file should include stuff like: File1 = Myfile.doc IsADir1 = No ByteSize1 = 3500 DateTimeStamp1 = 25.1.2001 14:54:31 File2 = Mydir IsADir2 = Yes DateTimeStamp2 = 1.5.2000 08:16:22 ByteDiskSpace = 3670016000 CurrentDir = C:\ADirectory It dosen't do anything however, because you haven't provided any command vocabulary of FTE.] ----------------------------------------------------------------------- [Explain the DSP source] ----------------------------------------------------------------------- [3 hours on FileLoc310] [Finnaly! After 3 long hours of debugging, FileLoc is finnaly functioning without a problem. It might seem long, but if you look at the LOG file the program generates, you will find what all does it acutaly do and how complex those tasks are! I'm suprized myself about the total buglessness.] [If the program troubles again at any time, please send over a copy of the newest LOG file!] ----------------------------------------------------------------------- [Thought A: 1. Transmit echo probe 2. Listen for the first echo probe 3. Send the command to the source of the first echo probe] [Thought B: - Status function - Send messages as CPU use changes - Up to 3 messages: - Idle - Normal - Overloaded - Reconfigure Console's node availability settings accordingly - Console: - Before each send, scan the node file for availability setting - Send or broadcast accordingly] [Which one? Both?] ----------------------------------------------------------------------- [1 hour on Data storage protocol] [DSP = a part of the Console, but used in all of ICI] [30 minutes on Console v275] [New DSP better supports serial entries; gap problem eliminated] [Succsess indicator: This bulk of code (gap problem): Found = False Do: N = N + 1 tmp$ = Data.xQuery(xNodesPath + "\" + TargetID.Text, "Function" + Trim$(Str$(N))) If UCase$(Trim$(tmp$)) = UCase$(Trim$(Param$(1))) Then Found = True: Exit Do Loop Until tmp$ = "" If Found Then Data.xRemoveEntry xNodesPath + "\" + TargetID.Text, "Function" + Trim$(Str$(N)) ': Debug.Print "Removing" Replaced with this (no problems whatsoever): Data.xRemoveSerial xNodesPath + "\" + TargetID.Text, "Function", UCase$(Trim$(Param$(1))) =) Tell me if you would want to have the DLL that does this.] ----------------------------------------------------------------------- [1 hour on Console v274] [Console can make use of FileLoc] [UDP restored] [Functions saved to node files] [No more questions during splash screen at least in theory] [Faster load] ----------------------------------------------------------------------- [1 hour on Console v273] [1 hour on FileLoc v211] ----------------------------------------------------------------------- [HELP!] [Function1 = A Function2 = B Function3 = C Remove B Function1 = A Function3 = C While reading, stops at first empty. This time 2!] [Ideas?] ----------------------------------------------------------------------- [1 hour on Console v271] [1 hour on ICIInstaller] [Updated Data Storage protocol] [30 minutes on Console v272] ----------------------------------------------------------------------- [Send over DLLs, EXEs] ----------------------------------------------------------------------- [news:comp.lang.basic.misc... How to include an ActiveX DLL in a project and what requires to be set to what again?] [Send DLLs around can do, because they're usefull only in ICI] Make sure that the Instancing property of the class module is not set to 1-Private, otherwise it will only be accessible to other modules within that same project. For most classes of this sort, you'll want to set the Instancing property to 5-MultiUse in order to use it from an ActiveX dll. Also make sure that any sub or function that you want to be a method is declared Public. Same goes for any variables you want to be visible to other programs. Although I'd recommend using property lets and gets for setting variables.