Just downloaded a fresh installer - still seg faulting - holler if you want 
the core posted again.


On Friday 22 June 2001 11:48, you wrote:
> All,
>
> This morning I caught up on most of the list. I noticed a lot of discussion
> about the installer
> (aside from the debian vs slack vs package management thread).
>
> Current version of the installer  is v3.0.3. Current version of Win4Lin is
> 3.0.3.
>
> Installer seg faults. A fix was being tested for one of the scenarios that
> was causing a seg fault, and now the seg faults are gone but it won't
> connect to the server - which
> ultimately might explain why the seg faults are no longer there.
>
> Here are a few brief but interesting (to some) things to know about the
> installer.
>
> When you run the installer the first time, you need to run it from whatever
> directory
> you downloaded it from. This will install a copy to
> /usr/bin/win4lin-install. Subsequent
> uses, should be run from the /usr/bin directory. If you are unsure or you
> are stuck in
> a continual installer update loop, verify you're running
> /usr/bin/win4lin-install. I have seen
> an instance or two where the installer will update itself twice back to
> back, but the third
> time it works. This mainly happens with v3.0.2, as v3.0.3 has a check that
> says, Hey I
> just updated myself, I'm not going to check for an update at this time.
>
> Once  you update win4lin-install, it copies the old version of itself to
> /usr/bin/win4lin-install.old.
> The installer downloads all it's files to /var/win4lin/installer_tmp. This
> includes the kernels and
> the win4lin updates.
>
> The installer is available for download through the members login of the
> www.netraverse.com.
>
> Regards,
> Mike
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to