Charles> The good news: I have XEmacs 21.0 "Pyrenean-pre8" built Charles> on Win32/MSVC6.0, with Jonathan Harris' unofficial EFS Charles> patches, and it mostly all works beautifully.... Charles> The bad news: it doesn't all quite work so beautifully. Charles> EFS works fine on my network, but I get these warnings: Charles> (1) (warning/warning) Error caught in Charles> `make-auto-save-file-name': Creating directory: No such Charles> file or directory, c:\home\cgw\home\cgw\/.autosave Yep, the current naming scheme for auto-save file names is not legal on WindowsNT's ````file system''''. You can get it to work by setting auto-save-directory nil. This works fine, except for performance when you edit files via NFS or EFS since the auto-save files are stored in the directory of the file it auto-saves. Charles> (HOME is /home/cgw; this is apparently getting doubled up Charles> somehow) Charles> Updating packages using EFS: XEmacs successfully fetches Charles> the .pkg.tar.gz files from xemacs.org, but when they are Charles> installed, I get a warning in the *Package Output* Charles> buffer: Charles> gunzip: stdout: Bad file number Charles> and the new package is not installed. Worse, the old Charles> files are removed from /Program Charles> Files/XEmacs/xemacs-packages and I'm left with no Charles> packages at all.... Charles> If updating packages via EFS is going to require a gunzip Charles> and tar, we better include suitable versions with the Charles> Windows distribution. I'm using the gunzip and tar from Charles> the Cygnus toolkit (in a non-Cygnus XEmacs) and they seem Charles> to be not suitable. Ditto for the FTP.EXE that comes Charles> with Cygnus: EFS works with \WINNT\System32\ftp.exe but Charles> not with the "ftp.exe" from Andy Piper's "local.tar.gz" Charles> distribution. -- Adrian Aichner European Design Center Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com