In message <[EMAIL PROTECTED]>, cn
<[EMAIL PROTECTED]> writes
>I much appreicate so many people's helps!
>
>OK. I have my job HALF done finally although in 0 & 1 world this means
>"not finished at all". I would like to feed back what I have experienced
>in win4lin beta 2:
>
>I am running a cloned Slackware distribution (from
>http://cle.linux.org.tw/) with kernel 2.2.13 and XFree86 4.01 in a
>no-brand notebook PC with AMD 500MHz.
>
>* The Trouble Shooting document says:
>The directory /opt/merge contains the files ...The directorys
>/var/merger contains the files...
>
see below

>** What I experienced:
>Directories /opt/merge and /var/merger do not exist at all. Perhaps this
>document needs revision for non-RPM distributions like Slackware.
>
>* The installation documentation says:
>Run "sh install-win4lin.sh"  after "rpm -i win4lin.rpm."
>
>** What I experienced:
>As suggested by Robert, "/opt/win4lin/postinst_rpm.sh" should be run
>instead of "sh install-win4lin.sh" because file install-win4lin.sh does
>not exist in my file system. This must be clearly written in the
>Installation Instruction for non-RPM distribution users.
>
see below

>** What I am told and follow:
>Slackware users need to create directories /etc/rc.d/rc2.d, rc3.d,
>rc4.d, rc5.d, init.d in /etc/rc.d prior to running "rpm -i win4lin.rpm".
>
>** What I experienced:
>Symolink libncurses.so.4 to libncurses.so.5 is necessary in my system.
>
yes, see below

>** What I experienced:
>I removed win4lin and re-installed it again.
>I did not run "winsetup&" in X this time. Instead, I ran "loadwindowsCD"
>without X. It seems that win4lin is finally properly installed and
>configured this time after about a week's work. Now command "dos" works
>and I can do some dos commands like "dir, cd" in dos window.
>
>My last win4lin problem which probably will not be solved in near
>future:
>I login as non-root user and start "win&". Then dialog "Windows is not
>installed. Do you want to install it now?" shows up. I then click on
>"OK" button and win4lin exits silently. I guess this is because win4lin
>does not support Chinese Windows yet. So I might have to wait Netraverse
>or turn to VMware for now.
>
>By the way, it took me aonther week to build and make rpm 4.0 to
>PARTIALLY work in my PC. Actually, command "rpm -e" does not work at
>all, and "rpm -i --nodeps" doe not work either for some package files
>like vmware.rpm. So, I removed rpm database first and issued "rm -r
>/var/win4lin /opt/win4lin" in place of "rpm -e" to remove win4lin.
>Perhaps rpm is too powerful for fools like me to use!
>
again, see below :-)

>Regards, Gurus.
>
>CN

Sorry to see you had such a hard time of it! 
I confess I had troubles first time, but that was some months ago,
before people appreciated eg the libncurses problem - hence the detailed
FAQ. (I had carefully installed a copy of genuine libncurses 4.0 since
win4lin appeared to be linked to it - DO NOT DO THIS :-), use a link to
libncurses5 - the confusion, explained in the wine FAQ (www.winehq.com)
is due apparently to Redhat meddling with package names to avoid
relinking). 

As a general rule, most slackware users advise steering clear of rpm's
(see alt.os.linux.slackware FAQ for instance) by converting via rpm2tgz
to .tgz format. (There's little advantage IMHO in installing rpms with
no dependency info in a distro using another package management system
for the rest of its software!) That does however leave you on your
initiative to find the right postinstall file to run ( - yes, I missed
it first time!) 

Finally, I doubt the reference to non-existent files like /var/merge has
anything to do with Slack. It's more a sign that the documentation
(which I think is generally good) was word-processed from the
'win4lin'-version (called merge) for SCO Unix, and the necessary change
(from merge to win4lin) not spotted.

Hope you find a compatible windows CD soon, as reward for your labours!
Bob 
-- 
robert w hall
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
http://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to