This license.txt issue has been around since Netraverse started using the .txt
file method of storing the user license. Nine out of ten times, the problem is
file format related and quite probably, caused by a missing cr/lf at the end 
of the last line.

For whatever reason, I have never suffered this problem and perhaps this is
due to the method used to make the license file. This method is very similar
to that mentioned in a previous message and is very simple. I use KDE2 and
KMAIL but the steps also worked with Netscape. The mail program is only used
to save the original copy of the file anyway.

First, remember to practice safe computing. I keep a copy of all my W4L files
in an archive directory on a separate disk and this is where I copied the
original email by using the save as feature. After this, I opened up a Konsole
started a root shell and executed Midnight Commander (my favorite utility)
and copied the new file to /var/win4lin/install/license-full.txt. Using the
built in editor I removed all the text up to and including the first line of
dashes. Then I removed all the text from and including the last line of dashes
leaving only the actual license text. Then a simple edit of my symlink
@license.txt to point to the new file. As a beta tester I wanted to keep the
beta license handy in case the registered license didn't work with beta
versions, thus the symlink. As it turned out, this wasn't really necessary
but I find the name license-full.txt and license-beta.txt to be easier for
me to remember and I don't have to view the files contents. This helps me
keep my backup files organized also.

For those who don't have Midnight Commander, most any file utility will work
to copy the text file. Likewise, any simple text editor should also work but
be careful the editor doesn't translate any control characters or have it's
own file format. Perhaps something like GMC/Cooledit or Kedit.

In the case of problems, you should check a few things before giving up. One,
make sure you have ALL the text between the two dashed lines starting at the
capital L in license and ending with the newline after the final data byte in
your KEY number. In MC, you can verify the file ending values by selecting F3
to view the file and F4 to see hex values. The file should end with 0A 0A.
This is the exact format of my file which works flawlessly.

Hope this helps some of you. BTW, you might want to save this text with your
backup license files to refresh you memory later on. You did make backups,
didn't you? :-)

On another note,
> kstart win --window Windows --geometry 1600x1138
>
> Kstart is a starter app that KDE provides. "win" of course starts win4lin. 
> Substitute your geometry for the 1600x1138, i.e. use 1024x768 if that is
> the window size you are shooting for. The "--window Windows" apparently
> keeps the command from affecting any other window - like the nag box that
> pops up before you license the product (which I had until the license.txt
> solution above). If you prefer launching from a command line then write a
> script to launch it with these commands.
>
> This works in KDE2 with Win4Lin 2, but of course ymmv.

I use KDE2, Xf86 3.36 on a custom RedHat 6.2 installation. I have never seen
the window issue, even with kpanel at the top of the screen and using the
autohide feature. However, even though launching win from a panel button with
the standard 'win' works well, it is only useful for launching W4L with the
default settings. In my case, it opens the dos window which then resizes the
window to match the Windows screen settings.

At first, running Windows in a window was cool but eventually I needed to go
back to the full 1280x1024 screen size. Under normal circumstances, window
managers such as KDE use borders and titles et al. which take up screen real
estate. Using kstart will help with this and here is my command line for a
full screen W4L in a KDE session.

kstart win --desktop 4 --window Windows --activate --type Override

To top it all off, I can launch this full screen Windows session without
using the fwin script or changing tty's or any of the problems associated
with starting a new X session with fwin. In fact, a simple click of a button
on the kpanel and I'm instantly switched to the Windows session. Load time is
minimal and definitely better than double booting the system. Even better,
with the KDE2 panel set to autohide, I can quickly jump to any Linux task by
moving the mouse to the top edge (or bottom as the case may be) and selecting
whatever and click as needed. It's like adding a whole new functionality to
Windows.

For those who want their users to start with Windows, this would be a great
setup. Just create a kdelnk file in the autostart directory which executes
this command line. With Linux's ability to automate other features, you could
easily configure the system to boot a user directly into Windows. Granted,
this is probably not a good idea, security wise but for a single user box that
doesn't need a network login, it should be fairly simple. Even with system
logins, it shouldn't be to difficult to setup.

Well, I hope all this rambling helps someone. Having used W4L for quite some
time I think it's the most remarkable Linux application I've used in awhile.
Certainly one of the most useful since the other folks here use Windows and I
as sysadmin elect have to deal with that.

Mike T
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to