Hello All, Before you all get upset, I know this has been discussed before, but I cannot find the answers. I downloaded the VMWare 3.0 beta. I have SuSE 7.2 now upgraded to 2.4.7-4GB kernel from ftp.suse.com. I am trying to install the beta. I searched and found the replacement for vmmon.tar (vmmon-for-2.4.7-only.tar.gz) and have followed the instructions to the T. However, when I run vmware-config.pl, it still complains it cannot find a suitable module for my kernel. Those of you who have successfully installed 2.04 under SuSE 7.2 w/2.4.7- 4GB kernel, could you point me in the right direction. I would be much obliged. Thank you in advance. Regards, Keith B.
On Friday 14 September 2001 12:45 pm, kbb0927@cs.com wrote:
Hello All,
Before you all get upset, I know this has been discussed before, but I cannot find the answers. I downloaded the VMWare 3.0 beta. I have SuSE 7.2 now upgraded to 2.4.7-4GB kernel from ftp.suse.com. I am trying to install the beta. I searched and found the replacement for vmmon.tar (vmmon-for-2.4.7-only.tar.gz) and have followed the instructions to the T. However, when I run vmware-config.pl, it still complains it cannot find a suitable module for my kernel.
Those of you who have successfully installed 2.04 under SuSE 7.2 w/2.4.7- 4GB kernel, could you point me in the right direction. I would be much obliged.
Thank you in advance. Regards,
Keith B.
I think you probably need the headers for the kernel.... I assume when it says it can't find an appropriate module that you let it try to compile one? Then maybe it can't find the headers? You'll have to get the headers from some place on SuSE. Since I never use the SuSE stuff for the kernel, I wouldn't have an answer for that. In my view, you should go straight to kernel.org and get their files and do the kernel from scratch. Much better-er. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/14/01 13:12 + +----------------------------------------------------------------------------+ 'I knew Doris Day before she was a virgin.' -- Oscar Levant
On Friday 14 September 2001 19.14, Bruce Marshall wrote:
In my view, you should go straight to kernel.org and get their files and do the kernel from scratch. Much better-er.
Why? What's in the vanilla kernel that makes it better? Or perhaps what's in the SuSE kernel that makes it worse? Anders
On Friday 14 September 2001 13:30 pm, Anders Johansson wrote:
On Friday 14 September 2001 19.14, Bruce Marshall wrote:
In my view, you should go straight to kernel.org and get their files and do the kernel from scratch. Much better-er.
Why? What's in the vanilla kernel that makes it better? Or perhaps what's in the SuSE kernel that makes it worse?
Anders
1) You get all the pieces. This is about the 5th response I've given to people who can't make things work with the SuSE pieces. (headers missing, etc) 2) You can compile it with your own choice of options. 3) Learn by doing. Suit yourself. I'd rather be in control of the kernel I use... and also be able to backtrack when I farkle something. I have read here of too many people who 'plug in' the new kernel from SuSE and things die with no easy method of retreat. Just my opinion and way of doing things. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/14/01 13:44 + +----------------------------------------------------------------------------+ "Apathy rules, but nobody can be bothered to do anything about it."
On Fri, 14 Sep 2001 13:47:46 -0400 Hello Bruce from Lourens: [snip] " > On Friday 14 September 2001 19.14, Bruce Marshall wrote: " > > In my view, you should go straight to kernel.org and get their " files and " > > do the kernel from scratch. Much better-er. " > " 1) You get all the pieces. This is about the 5th response I've " given to " people who can't make things work with the SuSE pieces. (headers " missing, " etc) " " 2) You can compile it with your own choice of options. " " 3) Learn by doing. [end snip] A question while this is being discussed - this vanilla vs SuSe thing has been bothering me (does'nt take much ...) - I installed kernel-source-2.4.7.SuSE-15.i386.rpm. - make cloneconfig (to see what options had been previously installed) - make xconfig, loaded the .config from the above and changed it to suit myself - blah, blah How would the end result from the above differ from the vanilla install? Thanks for your time Bruce. Bye. *** If you find a solution and become attached to it, the solution may become your next problem. *** Powered by SuSE Linux 7.2 Professional Registered Linux User Lourens Steenkamp Republic of South Africa _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Friday 14 September 2001 03:13 pm, Lourens Steenkamp wrote:
On Fri, 14 Sep 2001 13:47:46 -0400 --snip--
How would the end result from the above differ from the vanilla install?
--snip-- There are additional patches to the SuSE supplied kernels, that provide things like the twofish encrypted crypto filesystem, and a more recent SBLive! driver than is probably in the "stock" kernel. There are probably dozens of these updates across the entire kernel. In short, the SuSE kernel (in theory) should work better than the stock kernel. Have a great weekend, Steven -- -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Steven Hatfield http://www.knightswood.net Registered Linux User #220336 ICQ: 7314105 Useless Machine Data: Running SuSE Linux 7.2 Professional and KDE2.2 3:42pm up 1 day, 3:17, 2 users, load average: 2.69, 1.99, 1.57 -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Random Quote: Court Room Quotes Q: Are you married? A: No, I'm divorced. Q: And what did your husband do before you divorced him? A: A lot of things I didn't know about.
On Friday 14 September 2001 15:45 pm, Steven Hatfield wrote:
There are additional patches to the SuSE supplied kernels, that provide things like the twofish encrypted crypto filesystem, and a more recent SBLive! driver than is probably in the "stock" kernel. There are probably dozens of these updates across the entire kernel. In short, the SuSE kernel (in theory) should work better than the stock kernel.
To each his own.... I am not aware of anything I am missing. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/14/01 15:47 + +----------------------------------------------------------------------------+ "A classic is something that everybody wants to have read and nobody has read." - Mark Twain
On Friday 14 September 2001 03:48 pm, Bruce Marshall wrote:
On Friday 14 September 2001 15:45 pm, Steven Hatfield wrote:
There are additional patches to the SuSE supplied kernels, that provide things like the twofish encrypted crypto filesystem, and a more recent SBLive! driver than is probably in the "stock" kernel. There are probably dozens of these updates across the entire kernel. In short, the SuSE kernel (in theory) should work better than the stock kernel.
To each his own.... I am not aware of anything I am missing.
Go into "Block Devices" and look for "Twofish encryption for loop device". Is it there in the vanilla kernel? If it is, then maybe there isn't that much difference, but it's there in my SuSE kernel, and 3 of my filesystems are encrypted. If I were to go with the vanilla kernel, and it didn't have this, I wouldn't even be able to boot. Have a great weekend, Steven -- -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Steven Hatfield http://www.knightswood.net Registered Linux User #220336 ICQ: 7314105 Useless Machine Data: Running SuSE Linux 7.2 Professional and KDE2.2 3:51pm up 1 day, 3:26, 2 users, load average: 1.23, 1.45, 1.51 -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Random Quote: Education is what remains after one has forgotten everything he learned in school. -- A. Einstein
On Friday 14 September 2001 15:53 pm, Steven Hatfield wrote:
On Friday 14 September 2001 03:48 pm, Bruce Marshall wrote:
On Friday 14 September 2001 15:45 pm, Steven Hatfield wrote:
There are additional patches to the SuSE supplied kernels, that provide things like the twofish encrypted crypto filesystem, and a more recent SBLive! driver than is probably in the "stock" kernel. There are probably dozens of these updates across the entire kernel. In short, the SuSE kernel (in theory) should work better than the stock kernel.
To each his own.... I am not aware of anything I am missing.
Go into "Block Devices" and look for "Twofish encryption for loop device". Is it there in the vanilla kernel? If it is, then maybe there isn't that much difference, but it's there in my SuSE kernel, and 3 of my filesystems are encrypted. If I were to go with the vanilla kernel, and it didn't have this, I wouldn't even be able to boot.
Have a great weekend, Steven
I don't need it, therefore I am not missing it...... Simple as that. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/14/01 16:00 + +----------------------------------------------------------------------------+ "A man can do what he wants, but not want what he wants." - Arthur Schoperhauer
On Fri, 14 Sep 2001 15:45:02 -0400 Hello Steven from Lourens: " On Friday 14 September 2001 03:13 pm, Lourens Steenkamp wrote: " > On Fri, 14 Sep 2001 13:47:46 -0400 " --snip-- " > " > How would the end result from the above differ from the vanilla " install? " > " --snip-- " " There are additional patches to the SuSE supplied kernels, that " provide " things like the twofish encrypted crypto filesystem, and a more " recent " SBLive! driver than is probably in the "stock" kernel. There are " probably " dozens of these updates across the entire kernel. In short, the SuSE " kernel " (in theory) should work better than the stock kernel. " Thank you. While on the subject, in YAST2 -> Software -> Install/Remove software -> System Environment/Kernel there are two packages related to the kernel sources. One is "kernel-sources" ("The sources of the SuSE kernel"), the other is "linux" ("Rest of the kernel source code"). When I optimised my initial 2.4.4-4GB kernel for Atlon I only installed the former. What is included/purpose of the latter? Just curious. Bye. *** If you find a solution and become attached to it, the solution may become your next problem. *** Powered by SuSE Linux 7.2 Professional Registered Linux User Lourens Steenkamp Republic of South Africa _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Friday 14 September 2001 15:13 pm, Lourens Steenkamp wrote:
On Fri, 14 Sep 2001 13:47:46 -0400 Hello Bruce from Lourens:
[snip] " > On Friday 14 September 2001 19.14, Bruce Marshall wrote: " > > In my view, you should go straight to kernel.org and get their " files and " > > do the kernel from scratch. Much better-er. " > " 1) You get all the pieces. This is about the 5th response I've " given to " people who can't make things work with the SuSE pieces. (headers " missing, " etc) " " 2) You can compile it with your own choice of options. " " 3) Learn by doing. [end snip]
A question while this is being discussed - this vanilla vs SuSe thing has been bothering me (does'nt take much ...)
- I installed kernel-source-2.4.7.SuSE-15.i386.rpm. - make cloneconfig (to see what options had been previously installed) - make xconfig, loaded the .config from the above and changed it to suit myself - blah, blah
How would the end result from the above differ from the vanilla install?
Thanks for your time Bruce.
Bye.
If you load and configure from source, I suppose there is no difference.... It's the pre-compiled kernel's that are the problem I think. I have gathered this from others who were unable to install VMware on the higher kernels when pieces of it were missing. +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/14/01 15:42 + +----------------------------------------------------------------------------+ "He that is proud eats up himself; pride is his own glass, his own trumpet, his own chronicle." - William Shakespeare
Þann föstudagur 14 september 2001 19:45 skrifaðir þú:
On Friday 14 September 2001 15:13 pm, Lourens Steenkamp wrote:
On Fri, 14 Sep 2001 13:47:46 -0400 Hello Bruce from Lourens:
[snip] " > On Friday 14 September 2001 19.14, Bruce Marshall wrote: " > > In my view, you should go straight to kernel.org and get their " files and " > > do the kernel from scratch. Much better-er. " > " 1) You get all the pieces. This is about the 5th response I've " given to " people who can't make things work with the SuSE pieces. (headers " missing, " etc) " " 2) You can compile it with your own choice of options. " " 3) Learn by doing. [end snip]
A question while this is being discussed - this vanilla vs SuSe thing has been bothering me (does'nt take much ...)
- I installed kernel-source-2.4.7.SuSE-15.i386.rpm. - make cloneconfig (to see what options had been previously installed) - make xconfig, loaded the .config from the above and changed it to suit myself - blah, blah
How would the end result from the above differ from the vanilla install?
Thanks for your time Bruce.
Bye.
If you load and configure from source, I suppose there is no difference.... It's the pre-compiled kernel's that are the problem I think.
I have gathered this from others who were unable to install VMware on the higher kernels when pieces of it were missing.
Way wrong ! There is a LOT that differs. SuSE have done their own configuring ( and patching ) of the kernel. ( This was more true with 2.2.x than with 2.4.x but it's still true ). The "vanilla" source is just that - vanilla. If you are using any of the extended options in SuSE, you may well break them by using the vanilla sources. And.. to run VmWare, the ONLY change that has to be done is to enable CONFIG_MODVERSIONS=y Thus: ( if kernel-source-2.4.4.SuSE-17 ( or later ) is installed ) cd /usr/src/linux make cloneconfig mv .config .config.old sed 's/CONFIG_MODVERSIONS=n/CONFIG_MODVERSIONS=y/' < .config.old >.config make dep make bzImage cp ./arch/i386/boot/bzImage /boot/vmlinuz lilo shutdown -r now Should suffice, if and ONLY *IF*, you have installed the *SAME* kernel-sources as you have a binary running kernel !! ( otherwise make cloneconfig may give improper output for the new kernel ) -tosi
On Friday 14 September 2001 22.09, Tor Sigurdsson wrote:
Þann föstudagur 14 september 2001 19:45 skrifaðir þú:
On Friday 14 September 2001 15:13 pm, Lourens Steenkamp wrote:
On Fri, 14 Sep 2001 13:47:46 -0400 Hello Bruce from Lourens:
[snip] " > On Friday 14 September 2001 19.14, Bruce Marshall wrote: " > > In my view, you should go straight to kernel.org and get their " files and " > > do the kernel from scratch. Much better-er. " > " 1) You get all the pieces. This is about the 5th response I've " given to " people who can't make things work with the SuSE pieces. (headers " missing, " etc) " " 2) You can compile it with your own choice of options. " " 3) Learn by doing. [end snip]
A question while this is being discussed - this vanilla vs SuSe thing has been bothering me (does'nt take much ...)
- I installed kernel-source-2.4.7.SuSE-15.i386.rpm. - make cloneconfig (to see what options had been previously installed) - make xconfig, loaded the .config from the above and changed it to suit myself - blah, blah
How would the end result from the above differ from the vanilla install?
Thanks for your time Bruce.
Bye.
If you load and configure from source, I suppose there is no difference.... It's the pre-compiled kernel's that are the problem I think.
I have gathered this from others who were unable to install VMware on the higher kernels when pieces of it were missing.
Way wrong ! There is a LOT that differs.
SuSE have done their own configuring ( and patching ) of the kernel. ( This was more true with 2.2.x than with 2.4.x but it's still true ).
The "vanilla" source is just that - vanilla.
If you are using any of the extended options in SuSE, you may well break them by using the vanilla sources.
And.. to run VmWare, the ONLY change that has to be done is to enable CONFIG_MODVERSIONS=y
Thus: ( if kernel-source-2.4.4.SuSE-17 ( or later ) is installed )
cd /usr/src/linux make cloneconfig mv .config .config.old sed 's/CONFIG_MODVERSIONS=n/CONFIG_MODVERSIONS=y/' < .config.old >.config make dep make bzImage cp ./arch/i386/boot/bzImage /boot/vmlinuz lilo shutdown -r now
Should suffice, if and ONLY *IF*, you have installed the *SAME* kernel-sources as you have a binary running kernel !!
( otherwise make cloneconfig may give improper output for the new kernel )
-tosi
Is cloneconfig now in the vanilla kernel? I thought that was suse specific? Anders
Slightly off topic - if you have a Vanilla kernel, what files, or what could we cut and paste out of a file, that would enable us to keep a record of our current kernel config. Brian Marr On Saturday 15 September 2001 05:39, you wrote:
Þann föstudagur 14 september 2001 19:45 skrifaðir þú:
On Friday 14 September 2001 15:13 pm, Lourens Steenkamp wrote:
On Fri, 14 Sep 2001 13:47:46 -0400 Hello Bruce from Lourens:
[snip] " > On Friday 14 September 2001 19.14, Bruce Marshall wrote: " > > In my view, you should go straight to kernel.org and get their " files and " > > do the kernel from scratch. Much better-er. " > " 1) You get all the pieces. This is about the 5th response I've " given to " people who can't make things work with the SuSE pieces. (headers " missing, " etc) " " 2) You can compile it with your own choice of options. " " 3) Learn by doing. [end snip]
A question while this is being discussed - this vanilla vs SuSe thing has been bothering me (does'nt take much ...)
- I installed kernel-source-2.4.7.SuSE-15.i386.rpm. - make cloneconfig (to see what options had been previously installed) - make xconfig, loaded the .config from the above and changed it to suit myself - blah, blah
How would the end result from the above differ from the vanilla install?
Thanks for your time Bruce.
Bye.
If you load and configure from source, I suppose there is no difference.... It's the pre-compiled kernel's that are the problem I think.
I have gathered this from others who were unable to install VMware on the higher kernels when pieces of it were missing.
Way wrong ! There is a LOT that differs.
SuSE have done their own configuring ( and patching ) of the kernel. ( This was more true with 2.2.x than with 2.4.x but it's still true ).
The "vanilla" source is just that - vanilla.
If you are using any of the extended options in SuSE, you may well break them by using the vanilla sources.
And.. to run VmWare, the ONLY change that has to be done is to enable CONFIG_MODVERSIONS=y
Thus: ( if kernel-source-2.4.4.SuSE-17 ( or later ) is installed )
cd /usr/src/linux make cloneconfig mv .config .config.old sed 's/CONFIG_MODVERSIONS=n/CONFIG_MODVERSIONS=y/' < .config.old >.config make dep make bzImage cp ./arch/i386/boot/bzImage /boot/vmlinuz lilo shutdown -r now
Should suffice, if and ONLY *IF*, you have installed the *SAME* kernel-sources as you have a binary running kernel !!
( otherwise make cloneconfig may give improper output for the new kernel )
-tosi
You wouldn't have "make cloneconfig" But you could keep copies of your .config file in /usr/src/linux -tosi Þann föstudagur 14 september 2001 20:30 skrifaðir þú:
Slightly off topic - if you have a Vanilla kernel, what files, or what could we cut and paste out of a file, that would enable us to keep a record of our current kernel config.
Brian Marr
On Saturday 15 September 2001 05:39, you wrote:
Þann föstudagur 14 september 2001 19:45 skrifaðir þú:
On Friday 14 September 2001 15:13 pm, Lourens Steenkamp wrote:
On Fri, 14 Sep 2001 13:47:46 -0400 Hello Bruce from Lourens:
[snip] " > On Friday 14 September 2001 19.14, Bruce Marshall wrote: " > > In my view, you should go straight to kernel.org and get their " files and " > > do the kernel from scratch. Much better-er. " > " 1) You get all the pieces. This is about the 5th response I've " given to " people who can't make things work with the SuSE pieces. (headers " missing, " etc) " " 2) You can compile it with your own choice of options. " " 3) Learn by doing. [end snip]
A question while this is being discussed - this vanilla vs SuSe thing has been bothering me (does'nt take much ...)
- I installed kernel-source-2.4.7.SuSE-15.i386.rpm. - make cloneconfig (to see what options had been previously installed) - make xconfig, loaded the .config from the above and changed it to suit myself - blah, blah
How would the end result from the above differ from the vanilla install?
Thanks for your time Bruce.
Bye.
If you load and configure from source, I suppose there is no difference.... It's the pre-compiled kernel's that are the problem I think.
I have gathered this from others who were unable to install VMware on the higher kernels when pieces of it were missing.
Way wrong ! There is a LOT that differs.
SuSE have done their own configuring ( and patching ) of the kernel. ( This was more true with 2.2.x than with 2.4.x but it's still true ).
The "vanilla" source is just that - vanilla.
If you are using any of the extended options in SuSE, you may well break them by using the vanilla sources.
And.. to run VmWare, the ONLY change that has to be done is to enable CONFIG_MODVERSIONS=y
Thus: ( if kernel-source-2.4.4.SuSE-17 ( or later ) is installed )
.config make dep make bzImage cp ./arch/i386/boot/bzImage /boot/vmlinuz
cd /usr/src/linux make cloneconfig mv .config .config.old sed 's/CONFIG_MODVERSIONS=n/CONFIG_MODVERSIONS=y/' < .config.old lilo shutdown -r now
Should suffice, if and ONLY *IF*, you have installed the *SAME* kernel-sources as you have a binary running kernel !!
( otherwise make cloneconfig may give improper output for the new kernel )
-tosi
On Friday 14 September 2001 16:30 pm, Brian Marr wrote:
Slightly off topic - if you have a Vanilla kernel, what files, or what could we cut and paste out of a file, that would enable us to keep a record of our current kernel config.
The .config file in /usr/src/linux where /usr/src/linux usually points to ---> /usr/src/linux-2.4.x (your current kernel source) -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/14/01 18:38 + +----------------------------------------------------------------------------+ "Out of my mind. Back in five minutes."
Hello, I am sunning SuSE 7.2 on an iwill mainboard with built in sound. I recently recompiled my kernel with sound support (per instructions from SuSE and ALSA documentation). My new kernel functions quite well, but I see a few odd messages in /var/log/messages It was clearly stated that if functionality which was once module-ized and is now compiled into the kernel (like sound support), then you must remove the associated modules or odd results may occur. Where do I find these modules, and how do I know which ones to remove? Thanks, Dominic Here are the messages in /var/log/messages Sep 17 14:03:51 linux insmod: insmod: a module named snd-mixer-oss already exists Sep 17 14:03:51 linux insmod: insmod: insmod sound-service-0-0 failed Sep 17 14:03:51 linux insmod: insmod: a module named snd-mixer-oss already exists Sep 17 14:03:51 linux insmod: insmod: insmod sound-service-0-0 failed
I have installed VMWare 3.0 beta on my 7.2 machine today. You no longer need the 'special' vmmon patch but you need the kernel headers installed. When you install vmware, it will tell you it cannot find a proper module and offer to build one for you. Say yes and make sure the path it shows you is the correct one. There is also a bug I found in the installation. If you had version 2 running and you did not shut it down manually, the installation program does not remove the already loaded vmware modules and when it tries to load the new version it fails and tells you it could not find a proper module for your kernel. Avi --On Friday, September 14, 2001 12:45:56 PM -0400 kbb0927@cs.com wrote:
Hello All,
Before you all get upset, I know this has been discussed before, but I cannot find the answers. I downloaded the VMWare 3.0 beta. I have SuSE 7.2 now upgraded to 2.4.7-4GB kernel from ftp.suse.com. I am trying to install the beta. I searched and found the replacement for vmmon.tar (vmmon-for-2.4.7-only.tar.gz) and have followed the instructions to the T. However, when I run vmware-config.pl, it still complains it cannot find a suitable module for my kernel.
Those of you who have successfully installed 2.04 under SuSE 7.2 w/2.4.7- 4GB kernel, could you point me in the right direction. I would be much obliged.
Thank you in advance. Regards,
Keith B.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- Avi Schwartz avi@CFFtechnologies.com "I have to share the credit. I invented it, but Bill made it famous." - IBM engineer Dave Bradley describing the control-alt-delete reboot sequence
On Friday 14 September 2001 14:23 pm, Avi Schwartz wrote:
I have installed VMWare 3.0 beta on my 7.2 machine today. You no longer need the 'special' vmmon patch but you need the kernel headers installed. When you install vmware, it will tell you it cannot find a proper module and offer to build one for you. Say yes and make sure the path it shows you is the correct one.
There is also a bug I found in the installation. If you had version 2 running and you did not shut it down manually, the installation program does not remove the already loaded vmware modules and when it tries to load the new version it fails and tells you it could not find a proper module for your kernel.
As an added note, be sure to read the installation notes about the tools. There are definite steps to go through to get the new video driver installed. Part of which includes getting a blue screen and about 4 reboots. As an additional note, have once successfully installed the video driver, I had further driver problems later and finally scrapped any attempt to use 3.0 Beta. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/14/01 14:34 + +----------------------------------------------------------------------------+ Maah's Law: "Things go right so they can go wrong."
participants (9)
-
Anders Johansson -
Avi Schwartz -
Brian Marr -
Bruce Marshall -
Dominic Maraglia -
kbb0927＠cs.com -
Lourens Steenkamp -
Steven Hatfield -
Tor Sigurdsson