WordStar Discussion

WordStar for Windows => General Discussion => Topic started by: ostrowlaw on November 10, 2004, 04:57:34 AM

Title: WSWIN 2.0 on Novell Network
Post by: ostrowlaw on November 10, 2004, 04:57:34 AM
Hi,

Well, I've finally taken the plunge.  I have been using Wordstar 7.0 DOS on a Novell Netware network now for eons with no problems but lately there are some things that I need to do that I just can't do with a DOS program.  Primarily, Windows XP cut out my ability to copy text in the windows clipboard.  So, my question........

I copied all my files from my c:\wswin directory to a directory on the server's f: drive.  I actually moved them to a directory f:\apps\wswin and then I changed the wsw.ini  file to reflect the new directory.  It works fine on my computer.

Now, I'm ready to turn the other users loose.  Obviously, I need to make the files "read only and shareable".  Does anyone know if there are any files which need to be left in a "read/write" status?  The old WS Dos had several shared files in f:\ws\share that would be opened under names with $$$, temporary files.  Where are the temporary files housed in WSW (if at all) and which files need to be left R/W (if any).

Thanks.  I know this is a long-winded question but I don't leave too many questions here.

Alan
 ;D
Title: Re: WSWIN 2.0 on Novell Network
Post by: Forum Admin on November 10, 2004, 01:09:02 PM
The only files that WSWin updates are the wsw*.* and wsml.* files in the Windows directory. It also needs a path to TEMP and to WSWTEMP, both of which must be writable. If you use CG or AHD that may add to the list - I'm not sure. I have a feeling that these should be local to the machine WSWin is being run from, rather than on the server as it's not going to like having several people update these files at the same time.

Wouldn't you find it easier to install local copies of WSWin and just put the documents on the server?

Cheers
Mike
Title: Re: WSWIN 2.0 on Novell Network
Post by: ostrowlaw on November 10, 2004, 05:16:46 PM
Generally, you're right of course.  But, I find it easier as administrator to just have to keep track of one version, make changes to only 1 copy of the program and, most importantly, install only 1 copy.

"wsw*.* and wsml.* files in the Windows directory. It also needs a path to TEMP and to WSWTEMP".  So I assume then in the WSW.ini file I need to map a drive to each user's C:\temp and c:\wswtemp directories?  What about the WSW and WSMI files?  Are these files written to as part of useage of the program, or are they just read?

Thanks
Alan
 ???
Title: Re: WSWIN 2.0 on Novell Network
Post by: PGAGA on November 10, 2004, 06:34:13 PM
Wednesday, November 10, 2004

WSWin creates a its own temp folder under the system temp folder.  The name and location is declared in WSW.INI

             WswtempDirectory=c:\temp\wswtemp

Each time a file is opened a large number of temporary files are created which contain various aspects of the WSD file format (styles, fontnames, etc.).  The temporary files are compiled when a WSWin save is done.

Phil
Title: Re: WSWIN 2.0 on Novell Network
Post by: Forum Admin on November 10, 2004, 09:51:26 PM
wsw.ini contains paths to your folders, which toolbars are selected, which keystroke set you want to use, last documents edited list, toolbar and menu positions, etc. It will get written everytime you close WSWin.

wswin.cfg is the macro and keyboard shortcut assignments to keystrokes (menu assignments go in wsw.ini). This gets updated if you use the customise option for the toolbar, etc. It doesn't work correctly under Windows 2000 or XP.

wswset.ini lists items installed during initial program setup, so this doesn't change unless you re-run the setup program to change things.

wsml.ini is the maillist program's settings and lists the last active maillist database file. If you use Maillist, this may get updated on exit.

That's about it.

Cheers
Mike
Title: Re: WSWIN 2.0 on Novell Network;     WSWinDirector
Post by: ostrowlaw on November 11, 2004, 12:22:40 AM
Thanks Phil and Mike.  I rewrote my wsw.ini file to contain the following entries:

WSWinDirectory=f:\apps\wswin
PersonalDctDirectory=f:\apps\wswin\docs
Windows Readme Files=f:\windows; *.WRI;*.TXT
OpenDlgPath=F:\USERS\ARO
WSWinDirectory=f:\apps\wswin
TemplateDirectory=f:\apps\wswin\template
DocumentDirectory=f:\apps\wswin\docs
MacroDirectory=f:\apps\wswin\macros
MailListDirectory=f:\apps\wswin\maildata
;

I don't see any reference in this file to the temp file.  Obviously, I need to put in a config file somewhere that each user has access to his or own c:\temp or c:\wswin\temp directory for the temp files, so that all the users on the network don't access the same files at the same time.  Otherwise, this will not be a true networked program.

Thanks
Alan
Title: Re: WSWIN 2.0 on Novell Network
Post by: ostrowlaw on November 11, 2004, 12:24:52 AM
Ok, Phil already answered this question:   WswtempDirectory=c:\temp\wswtemp
I'll put this in the wsw.ini file and this should take care of it.  Now, one last thing, does this wsw.ini file go in each user's c:\windows directory, or does it go in the f:\apps\wswin directory?

Thanks
Alan
 ;D
Title: Re: WSWIN 2.0 on Novell Network
Post by: PGAGA on November 11, 2004, 01:26:24 AM
Wednesday, November 10, 2004

WSW.ini is normally in the C:\windows or c:\WinNT folder, but can be in the WSWin folder if the WSWin folder is declared as part of the object properties.

Phil
Title: Re: WSWIN 2.0 on Novell Network
Post by: ostrowlaw on November 11, 2004, 01:33:46 AM
That's what I thought, because every time I copied it into the file server's hard disk to f:\apps\wswin, it seemed to disappear when the program was restarted (another mystery!!!).  So, I guess that the wsw*.* files need to be copied into each user's directory, with the bulk of the program files, etc. onto the server's hard disk?

Thanks
Alan
 8)
Title: Re: WSWIN 2.0 on Novell Network
Post by: Forum Admin on November 11, 2004, 03:05:45 PM
That would make more sense because when any user changes any setting that gets saved in wsw.ini (window position or size, toolbar position, recently opened files, etc) you need those settings for that user not just the last one to do anything.

Please let us know how it all works - assuming it does!


Cheers
Mike
Title: Re: WSWIN 2.0 on Novell Network
Post by: ostrowlaw on November 11, 2004, 10:06:11 PM
Well, I would have reported back to you today that all was finished, but there's no sense even giving the hordes access to the program until all the macros are finished.  Also, need to program the function keys with "idiot commands" for the masses here.  Just kidding, but we do try to accomodate the computer challenged.  Since I'm working on the macros at home, and they don't seem to be cooperating, I guess it'll be a few more days.

I question whether this is even worth it.  I note that there is template for MS Word commands to WS commands.  Maybe this is the smarter (and more modern) way to go, and I can spend my time converting the old WS files to Word, instead of diddling around with installation issues, compatibility issues, macro incompatibilies, etc.????

 ;D

Title: Re: WSWIN 2.0 on Novell Network
Post by: Forum Admin on November 12, 2004, 08:11:50 PM
If your main goal is to keep using WordStar commands rather than to continue using existing WordStar templates, macros, etc., then the command emulator may do what you need. It's not a 100% WordStar clone in terms of use as Windows and Word work in a completely different way and so some commands just aren't directly comparable. I've worked around these issues to give as faithfull a WordStar command set as possible, but there are a few small differences.

If you do decide to try the emulator out (it works with all Word for Windows versions from Word 97 onwards) I'd suggest that you give the evaluation version (you can download it from: http://www.wordstar.org/wsemu/word/downloads/word97/wordstar.zip) a quick try out to get a general feel for it, and also printout the FAQ page http://www.wordstar.org/wsemu/word/pages/faq.htm to see what the full version does and doesn't do.

To get your existing files converted, you'll need the import filters, which Microsoft has now withdrawn from general distribution. The WordStar ones are still available on its ftp site though: ftp://ftp.microsoft.com/softlib/mslfiles/wdsupcnv.exe. This link sometimes fails, so you may need to try several times before you get the file downloaded. Full instructions for its use are detailed at: http://www.wordstar.org/wordstar/pages/convert_faq.htm#Q3 - don't worry that this says it's for Word 95, the filters never got updated after that and still work in Word 2003.

Cheers
Mike