Installing TDK 4.0.4 trial with Tcl 8.5.1...

Hi all,

In my system, I got:

Initialize TclApp TAP search preferences
# c:\program files (x86)\tcl\lib\tcl8.5
# c:\program files (x86)\tcl\lib

Locate an ActiveTcl 8.4.9.1+ installation for use by the Tcl Dev Kit demos.

The Tcl Dev Kit demos are impaired and will not work. They rely on the
presence of a suitable installation of ActiveTcl (8.4.9.1+). Such an
installation was not found.

Is this normal? I have 8.5, why the requirement 8.4.9.1+ is not satisfied?

Then the TDK installer continues with:

Extending the registry ...
Adding recognition of .tpj files ...
Adding recognition of .tap files ...
Adding recognition of .tdk files ...
Adding recognition of .txr files ...
Adding "C:\Program Files (x86)\TclDevKit\bin" to your executable path ...
Adding ".tcl" to your pathext ...
(".tcl" already in your pathext)
Register uninstaller in system
* No bwidget package found in selected ActiveTcl
* No tcllib package found in selected ActiveTcl
* No Img package found in selected ActiveTcl

Another wrong result. In my wish, I get the following:

(bin) 1 % package req BWidget
1.8
(bin) 2 % package req Img
1.3

And finally some more errors (which I relate to the inability to install correctly under vista 64):

Creating program group "ActiveState Tcl Dev Kit 4.0.4" ...
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: remote server cannot handle this command
ERROR: Unable to determine name of link file for "Xref BWidgets"
ERROR: Unable to determine name of link file for "Tcllib"
ERROR: Unable to determine name of link file for "Img"
ERROR: remote server cannot handle this command

You can see the installation results at:
http://www.ellogon.org/~petasis/tcl/TDK.png

It seems that Tcl/Tk 8.5.1 can be installed fine under vista 64, but TDK 4.0.4 does not at the moment. It is completely unusable from the start menu :-(

George
.

Relevant Pages

  • Re: Installing TDK 4.0.4 trial with Tcl 8.5.1...
    ... Locate an ActiveTcl 8.4.9.1+ installation for use by the Tcl Dev Kit demos. ... Then the TDK installer continues with: ... remote server cannot handle this command ...
    (comp.lang.tcl)
  • Re: Installing TDK 4.0.4 trial with Tcl 8.5.1...
    ... Locate an ActiveTcl 8.4.9.1+ installation for use by the Tcl Dev Kit demos. ... No bwidget package found in selected ActiveTcl ... remote server cannot handle this command ...
    (comp.lang.tcl)
  • Re: CPU Node board failure on Origin 2000
    ... you'll have a single machine. ... I cant believe that you can run a system which uses partition without the MMSC because the MMSC is needed to shotdown and restart a specific partion. ... This looks like and older IRIX installation because latest PROM is 6.156 from Nov 18, ... So you have to asign the ids manually by enter the command line modus from the maintenance menu. ...
    (comp.sys.sgi.hardware)
  • Re: How can i install and boot to MS-DOS
    ... Debug is an ancient command that is included in almost all versions of MS-DOS, is it part of your DOS installation? ... Another way of creating the multi-boot is to start a Windows XP installation from the up and booted MS-DOS installation and then aborting the installation before the first reboot. ... To launch the XP setup from DOS insert the CD in the drive and navigate to the i386 directory and launch the Winnt command. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Windows XP boots to background only, no start button, no icons
    ... I tried the cacls command for explorer.exe and it showed that users & power ... about not having the right permissions. ... but I can access my task manager. ... use your system CD to do a repair installation. ...
    (microsoft.public.windowsxp.general)