Functions which no-one has ever tried to use....

[Charles Dye]

@IPPORT and @IPZONEID. It looks like neither one has ever worked, and nobody has ever noticed.

@IPZONEID is funny. It seems to be picking up the IPv6 scope correctly, and then returning it as an error code. If adapter #0 has an IP address ending in %12, then @IPZONEID emits an "access code is invalid" error, and so on.

@IPPORT looks like it's about 99% there. Pass it a valid service name like "http" or "imap4" or "gopher", and it returns ... without changing the string buffer, so you just get the same string back. But an unknown service name gives an error message. So I think the code is requesting and getting the required data from Windows, and then blissfully exiting.

If both functions were removed and de-documented, I doubt if anyone would notice that, either. Priority: Iron your shoelaces first.

 

[vefatica]

Hmmm! I get this.

v:\> echo %@ipzoneid[0]
TCC: (Sys) An attempt was made to load a program with an incorrect format.
 "%@ipzoneid[0]"

 

[Charles Dye]

Hmmm! I get this.

v:\> echo %@ipzoneid[0]
TCC: (Sys) An attempt was made to load a program with an incorrect format.
 "%@ipzoneid[0]"

I'm guessing that the IPv6 address for that adapter ends in %11 ...?

 

[vefatica]

How do I find out? IPCONFIG /ALL shows only the "6TO4" adapter as having an IPV6 address.

And what's "%11"? All the IPV6 addresses I've seen look like that below.

Off topic, but I hope someone can shed some light ... I have two internet connections, neither of which have IPV6 bound.

But I see it in use (to whom else but Google). From NETSTAT -ano ...

TCP    [2002:48e6:5495::48e6:5495]:58831  [2607:f8b0:4006:819::2002]:443  ESTABLISHED
TCP    [2002:48e6:5495::48e6:5495]:58833  [2607:f8b0:4006:810::2003]:443  ESTABLISHED
TCP    [2002:48e6:5495::48e6:5495]:58835  [2607:f8b0:4006:813::200e]:443  ESTABLISHED

I also see IPV6 DNS info cached when I use "IPCONFIG /DISPLAYDNS".
Does anyone know what's going on?

 

[vefatica]

@IPZONEID is rather fun. I get a different error message for each parameter I give it.

v:\> echo %@ipzoneid[0]
TCC: (Sys) An attempt was made to load a program with an incorrect format.
 "%@ipzoneid[0]"

v:\> echo %@ipzoneid[1]
TCC: (Sys) The access code is invalid.
 "%@ipzoneid[1]"

v:\> echo %@ipzoneid[2]
TCC: (Sys) Incorrect function.
 "%@ipzoneid[2]"

v:\> echo %@ipzoneid[3]
TCC: (Sys) The data is invalid.
 "%@ipzoneid[3]"

v:\> echo %@ipzoneid[4]
TCC: (Sys) Not enough storage is available to complete this operation.
 "%@ipzoneid[4]"

v:\> echo %@ipzoneid[5]
TCC: (Sys) The system cannot find the drive specified.
 "%@ipzoneid[5]"

 

[Charles Dye]

Both working as I would expect in build 29.