If you have some "killer apps" on Windows that you don't want to move from, it may be worth a giggle to see if they are supported on Linux by using WINE. In the days of old, the fastest combination to run the old s@h 'screensaver' cruncher was to run the Windows application on WINE on a Linux OS!
Not exactly a comparable example but still interesting for a giggle:
... The problem Microsoft faced with its Top 500 ranking is that the achievement wasn't recognized because the same machine was able to achieve higher speeds using Linux. General manager of Microsoft's technical computing group Bill Hilf said that the benchmarking tests were performed on both Linux and Windows with a resulting 5-percent difference, however Linux came out on top. That said, the Tokyo Institute was only allowed to submit one test to the Top 500 group, and obviously chose the faster of the two...
I use a four port KVM switching between 4 servers and all works fine across various flavours/versions of Mandriva. ...There are more distros than just Kubuntu/Ubuntu.
If you want an "LTS" edition, the Kubuntu 10.04LTS should work well.
I'm already running the LTS edition of Kubuntu v10.04, on my Linux PC. I had first read about Ubuntu in PC World and thought I would give it a try. My first *nix type OS was FreeBSD. Although I had it on 2 different PCs, there was a very high learning curve involved in the configuration. I had a hard time understanding what I was doing. That was about 6 years ago.
I went ahead, about 3 years ago, with Ubuntu. The one thing I didn't like about it was the GUI, Gnome if memory serves. I had KDE installed on the FreeBSD PCs and liked it. So, I installed KDE on the Ubuntu PC. Then I discovered Kubuntu which already has KDE installed when installing the OS. Been with it ever since. It is my Linux preference. :)
Quote:
Very strange that you associate starting a fourth application for causing the KVM problem... But then if you need to use the KVM, then that's a killer.
For KVM hardware problems, don't forget that the problem can be in a lead/connector and not just the box itself...
Martin, I know you're trying to help, and I really appreciate it, really. :) But, wouldn't it be logical to determine that there is nothing wrong with the KVM or anything related to it since the problem is associated to only one OS on a dual-boot PC? When the keyboard and mouse lock up in v10.10 on the i7, I switch to v10.04 on the Linux PC and the keyboard and mouse are working just fine. I switch back to the i7 and they're still locked up. I'm on the v10.04 PC right now and have been for the better part of 2 hours. With more than 3 apps running on v10.10, they lock up. I have had as many as 5 or 6 going at once in the v10.04 without a problem. I've had as many or more going at once in WinXP and no problems.
I can replicate the occurrence right now by starting up 2 more apps, in v10.10, on the i7. But, the i7 has been BOINCing for better than 24 hours and I would like to see what the uptime will be when the WUs are finished. That is my main objective right now. When it's done, I will no longer be running v10.10, so the keyboard / mouse lock up issue is somewhat moot.
Quote:
If you have some "killer apps" on Windows that you don't want to move from, it may be worth a giggle to see if they are supported on Linux by using WINE. In the days of old, the fastest combination to run the old s@h 'screensaver' cruncher was to run the Windows application on WINE on a Linux OS!
I only have one "killer app" and it only comes in Windoze and Mac versions. I did try that app in Wine on Linux. It crashed the computer after about 30 to 45 minutes. I decided not to take that road again.
Quote:
Good luck,
Martin
Thanks Martin! :) The i7 is just over 25 hours and counting. I believe that effectively discounts any possibility of failing hardware. Wouldn't you say? :)
Would it not be more accurate to say that the compiler used for the Linux copy of the application beat out the one used for Windows?
Surely you don't think either OS has anywhere near 5% inherent overhead for this sort of work?
Can be.
For example, Linux has a O(0) ("zero-order") scheduler. That is, regardless of the number of jobs waiting to be scheduled, the Linux scheduler will schedule them all always in the same amount of time. If for example the Windows scheduler needs linear time ("O(1)") per number of jobs to do it's scheduling, that could easily cripple performance when scheduling thousands of jobs. Similarly so for other tasks such as process communication, memory management and so on...
For desktop use, with just a few tasks to manage, the most important aspects for kernel performance are reliability and security. The efficiency of how the kernel does things there is not so important. However, in a server or 'supercomputer' environment where very many tasks must be managed in parallel, good design (as with most things) can give a significant performance boost.
... For KVM hardware problems, don't forget that the problem can be in a lead/connector and not just the box itself...
... But, wouldn't it be logical to determine that there is nothing wrong with the KVM or anything related to it since the problem is associated to only one OS on a dual-boot PC?...
I've seen a dodgy connector where it would become intermittent only when you pushed one particular switch on a control panel. Pushing another switch remade the contact on the unassociated connector. Talk about dreaming metaphysical connections across the panel! A bit like turning on your house light switch for the lights but also the washing machine springing to life!! Disassembly and reassembly showed a short pin on one connector getting flexed out of it's socket as the panel flexed in a certain way. Flexing the panel another way pushed the troublesome pin back against the edge of the socket to make a good contact...
Try swapping the leads around on the KVM, and swapping ports, to eliminate any one component/connector possibly being the problem.
Quote:
I can replicate the occurrence right now by starting up 2 more apps, in v10.10, on the i7.
If consistently repeatable, then that must be a bug of some sort that needs tracing and squashing! I'm sure the kernel devs list will be interested in that one.
Quote:
But, the i7 has been BOINCing for better than 24 hours and I would like to see what the uptime will be when the WUs are finished. That is my main objective right now. When it's done, I will no longer be running v10.10, so the keyboard / mouse lock up issue is somewhat moot.
Good going there and great if it fixes your problem.
The KVM switch bug should at least be reported if only to warn others of the potential problem.
Well, BOINC, on the Linux side of the i7, has finished without the problem I was having on the WinXP side of things, save for the random mouse and keyboard lock up discussed previously. On to my clean re-installation of WinXP Pro. Which, by the way, will be a temporary gig until next year when I get Win7 Pro 64 bit. :)
Now, for a disturbing discovery: When I installed Kubuntu v10.10 for the dual-boot test purpose, I found that it was NOT installed where the install app said it was going, where I assumed it was going. It told me it would split my boot drive, drive c:\, in half and place Linux on the second half of the boot drive. WRONG!
I just found out that the partitioning took place on my second drive, where I keep my backup stuff from Windoze, all my personal stuff. And, not only that, it made 2 partitions on the second half, which I assume would be the case under "normal" installation circumstances. So, now I have to reclaim those 2 partitions so that I have access to the FULL drive, through Windoze, and not just half of it. This will delay my clean re-installation of WinXP Pro!
Murphy needs a good slapping upside the head! ;)
@ Martin: I will keep observing the mouse and keyboard problem. Although it is not a problem through Windoze or the Core 2 Duo Linux PC, if I don't see anything, I will try to contact someone of the Kubuntu community to report the problem with v10.10. Although, I'm sure they already know, since I found so much about it on the Internet.
By the way, the i7 with v10.10 ran for 37.5 hours before the next mouse and keyboard lock up, then another 17 hours, for BOINC to finish, without the lock up. And the problem observed when running BOINC in Windoze never appeared. :)
Keep on BOINCing...! :) (the i7 will be within the next 6 hours or so :) )
Well, BOINC, on the Linux side of the i7, has finished without the problem I was having on the WinXP side of things, save for the random mouse and keyboard lock up discussed previously. On to my clean re-installation of WinXP Pro. Which, by the way, will be a temporary gig until next year when I get Win7 Pro 64 bit. :)
Now, for a disturbing discovery: When I installed Kubuntu v10.10 for the dual-boot test purpose, I found that it was NOT installed where the install app said it was going, where I assumed it was going. It told me it would split my boot drive, drive c:\, in half and place Linux on the second half of the boot drive. WRONG!
I just found out that the partitioning took place on my second drive, where I keep my backup stuff from Windoze, all my personal stuff. And, not only that, it made 2 partitions on the second half, which I assume would be the case under "normal" installation circumstances. So, now I have to reclaim those 2 partitions so that I have access to the FULL drive, through Windoze, and not just half of it. This will delay my clean re-installation of WinXP Pro!
Murphy needs a good slapping upside the head! ;)
@ Martin: I will keep observing the mouse and keyboard problem. Although it is not a problem through Windoze or the Core 2 Duo Linux PC, if I don't see anything, I will try to contact someone of the Kubuntu community to report the problem with v10.10. Although, I'm sure they already know, since I found so much about it on the Internet.
By the way, the i7 with v10.10 ran for 37.5 hours before the next mouse and keyboard lock up, then another 17 hours, for BOINC to finish, without the lock up. And the problem observed when running BOINC in Windoze never appeared. :)
Keep on BOINCing...! :) (the i7 will be within the next 6 hours or so :) )
I wonder if the kvm switch is your Windows problem too, you say it ran just fine for 37.5 hours then again for 17 hours before it locked up under Linux. I wonder if it was locking up under windows but because of the way it locked up you had to reset the machine to make it work again? The way to know is to plug the keyboard and mouse in to the pc directly and let it run that way for as long as it does without crashing. Since you are happiest with Linux right now try that for the next 4 days, then switch to Windows and see how long it runs without crashing. If it makes it 4 days under Linux then I would guess that it fixed that problem, but Windows will be the key test, will it work or crash?
Well, BOINC, on the Linux side of the i7, has finished without the problem I was having on the WinXP side of things, save for the random mouse and keyboard lock up discussed previously. On to my clean re-installation of WinXP Pro. Which, by the way, will be a temporary gig until next year when I get Win7 Pro 64 bit. :)
Now, for a disturbing discovery: When I installed Kubuntu v10.10 for the dual-boot test purpose, I found that it was NOT installed where the install app said it was going, where I assumed it was going. It told me it would split my boot drive, drive c:\, in half and place Linux on the second half of the boot drive. WRONG!
I just found out that the partitioning took place on my second drive, where I keep my backup stuff from Windoze, all my personal stuff. And, not only that, it made 2 partitions on the second half, which I assume would be the case under "normal" installation circumstances. So, now I have to reclaim those 2 partitions so that I have access to the FULL drive, through Windoze, and not just half of it. This will delay my clean re-installation of WinXP Pro!
Murphy needs a good slapping upside the head! ;)
@ Martin: I will keep observing the mouse and keyboard problem. Although it is not a problem through Windoze or the Core 2 Duo Linux PC, if I don't see anything, I will try to contact someone of the Kubuntu community to report the problem with v10.10. Although, I'm sure they already know, since I found so much about it on the Internet.
By the way, the i7 with v10.10 ran for 37.5 hours before the next mouse and keyboard lock up, then another 17 hours, for BOINC to finish, without the lock up. And the problem observed when running BOINC in Windoze never appeared. :)
Keep on BOINCing...! :) (the i7 will be within the next 6 hours or so :) )
I wonder if the kvm switch is your Windows problem too, you say it ran just fine for 37.5 hours then again for 17 hours before it locked up under Linux. I wonder if it was locking up under windows but because of the way it locked up you had to reset the machine to make it work again? The way to know is to plug the keyboard and mouse in to the pc directly and let it run that way for as long as it does without crashing. Since you are happiest with Linux right now try that for the next 4 days, then switch to Windows and see how long it runs without crashing. If it makes it 4 days under Linux then I would guess that it fixed that problem, but Windows will be the key test, will it work or crash?
Greetings Mikey,
I cannot run the test you suggest since Linux no longer exists on the i7. But, the problem I had with the mouse and keyboard locking up in Linux, is now the least of my worries (see update below).
*** UPDATE ***
I have recovered all but 5.334 GB of the space on my second HDD where, for whatever odd reason, Kubuntu v10.10 was installed. Since both my HDDs are 500 GB drives, I'm not concerned with that unused 5 GB.
During my clean re-installation of WinXP Pro, I decided to do the extended format of the boot drive, just to be sure there was no lingering bad code anywhere on it. Formatting took well over 2 hours to complete. WinXP installed without a problem. I installed my various drivers from my install CD that came with the MoBo. All went well, no artifacts appeared on the "cylon" splash screen. Then...
I decided to install my nVIDIA driver(s) from the downloaded update version instead of from the CD that came with the video card. Guess what? Upon reboot, the artifact came back to the "cylon" screen. :( Ok, this tells me that there is a problem somewhere in the driver / software code driving my video card. I tried to roll back the driver to the one WinXP installed and was using only to find out that no driver files were backed up for that purpose. Bummer... :(
Now, here's something a bit odd: It now takes a few minutes for my network icon to show up in the notification area. Before doing all the myriad updates from Micro$oft, it would appear very shortly after my firewall and virus scanner were running. It still shows up after, just a few minutes after, now.
I have not installed BOINC yet and will wait until I can figure out how to fix my "video problem". The problem with uninstalling nVIDIA is that I will no longer have sound, not that that is a really important factor. I just hate seeing the yellow "?"s in Device Manager. ;) I really don't have much use for sound, yet. I fail to understand why nVIDIA would have anything whatsoever to do with sound. I assumed that installing the sound driver(s) from the MoBo CD would suffice, since the sound is an integrated device on the MoBo. Hmmm... Just had a thought: I wonder if I could peek around on my nVIDIA CD and find the files needed for the sound and somehow get them installed. Then again, what's to say that THEY aren't what causes the artifact to show up on the "cylon" splash screen. :/
All in all, though, the i7 seems to be running just fine, despite what I have mentioned above. It boots faster, applications launch faster, etc.
Hmmm... I was just thinking of the past and seem to remember the artifact problem with WinXP Home on the Core 2 Duo as well. It, too, had a video card with nVIDIA technology and driver(s). Same with WinXP Pro on that same PC. Perhaps it is time to switch to another brand of video technology. ATI perhaps?
At least my mouse and keyboard ain't locking up on me now... :)
Well, BOINC, on the Linux side of the i7, has finished without the problem I was having on the WinXP side of things, save for the random mouse and keyboard lock up discussed previously. On to my clean re-installation of WinXP Pro. Which, by the way, will be a temporary gig until next year when I get Win7 Pro 64 bit. :)
Now, for a disturbing discovery: When I installed Kubuntu v10.10 for the dual-boot test purpose, I found that it was NOT installed where the install app said it was going, where I assumed it was going. It told me it would split my boot drive, drive c:\, in half and place Linux on the second half of the boot drive. WRONG!
I just found out that the partitioning took place on my second drive, where I keep my backup stuff from Windoze, all my personal stuff. And, not only that, it made 2 partitions on the second half, which I assume would be the case under "normal" installation circumstances. So, now I have to reclaim those 2 partitions so that I have access to the FULL drive, through Windoze, and not just half of it. This will delay my clean re-installation of WinXP Pro!
Murphy needs a good slapping upside the head! ;)
@ Martin: I will keep observing the mouse and keyboard problem. Although it is not a problem through Windoze or the Core 2 Duo Linux PC, if I don't see anything, I will try to contact someone of the Kubuntu community to report the problem with v10.10. Although, I'm sure they already know, since I found so much about it on the Internet.
By the way, the i7 with v10.10 ran for 37.5 hours before the next mouse and keyboard lock up, then another 17 hours, for BOINC to finish, without the lock up. And the problem observed when running BOINC in Windoze never appeared. :)
Keep on BOINCing...! :) (the i7 will be within the next 6 hours or so :) )
I wonder if the kvm switch is your Windows problem too, you say it ran just fine for 37.5 hours then again for 17 hours before it locked up under Linux. I wonder if it was locking up under windows but because of the way it locked up you had to reset the machine to make it work again? The way to know is to plug the keyboard and mouse in to the pc directly and let it run that way for as long as it does without crashing. Since you are happiest with Linux right now try that for the next 4 days, then switch to Windows and see how long it runs without crashing. If it makes it 4 days under Linux then I would guess that it fixed that problem, but Windows will be the key test, will it work or crash?
Greetings Mikey,
I cannot run the test you suggest since Linux no longer exists on the i7. But, the problem I had with the mouse and keyboard locking up in Linux, is now the least of my worries (see update below).
*** UPDATE ***
I have recovered all but 5.334 GB of the space on my second HDD where, for whatever odd reason, Kubuntu v10.10 was installed. Since both my HDDs are 500 GB drives, I'm not concerned with that unused 5 GB.
During my clean re-installation of WinXP Pro, I decided to do the extended format of the boot drive, just to be sure there was no lingering bad code anywhere on it. Formatting took well over 2 hours to complete. WinXP installed without a problem. I installed my various drivers from my install CD that came with the MoBo. All went well, no artifacts appeared on the "cylon" splash screen. Then...
I decided to install my nVIDIA driver(s) from the downloaded update version instead of from the CD that came with the video card. Guess what? Upon reboot, the artifact came back to the "cylon" screen. :( Ok, this tells me that there is a problem somewhere in the driver / software code driving my video card. I tried to roll back the driver to the one WinXP installed and was using only to find out that no driver files were backed up for that purpose. Bummer... :(
Now, here's something a bit odd: It now takes a few minutes for my network icon to show up in the notification area. Before doing all the myriad updates from Micro$oft, it would appear very shortly after my firewall and virus scanner were running. It still shows up after, just a few minutes after, now.
I have not installed BOINC yet and will wait until I can figure out how to fix my "video problem". The problem with uninstalling nVIDIA is that I will no longer have sound, not that that is a really important factor. I just hate seeing the yellow "?"s in Device Manager. ;) I really don't have much use for sound, yet. I fail to understand why nVIDIA would have anything whatsoever to do with sound. I assumed that installing the sound driver(s) from the MoBo CD would suffice, since the sound is an integrated device on the MoBo. Hmmm... Just had a thought: I wonder if I could peek around on my nVIDIA CD and find the files needed for the sound and somehow get them installed. Then again, what's to say that THEY aren't what causes the artifact to show up on the "cylon" splash screen. :/
All in all, though, the i7 seems to be running just fine, despite what I have mentioned above. It boots faster, applications launch faster, etc.
Hmmm... I was just thinking of the past and seem to remember the artifact problem with WinXP Home on the Core 2 Duo as well. It, too, had a video card with nVIDIA technology and driver(s). Same with WinXP Pro on that same PC. Perhaps it is time to switch to another brand of video technology. ATI perhaps?
At least my mouse and keyboard ain't locking up on me now... :)
Keep on BOINCing...! :)
Are you trying to use the 'latest and greatest' Nvidia drivers? If so drop back a step or 2 or even 3 and see if they work better, sometimes the 'latest and greatest' is not! As for the network icon do the Windows updates, ALL OF THEM, and I thought the 'dot net' stuff was part of that fix. As for your sound card try doing a manual update thru the Device Manager and tell it look in Windows Update when it asks.
Things ALWAYS run faster after a fresh install because none of the little things that we load over the long term are loaded yet. Try to keep things like quicktime, adobe reader, etc, etc, etc from loading prior to you actually needing them. You can do this by editing the Msconfig file, you get there by clicking start, then run and typing msconfig on the line and pressing enter. BE CAREFUL THOUGH. Whatever you change, and ONLY CHANGE things in the Startup section, WILL affect the way the machine runs and IF it boots!!! I ALWAYS uncheck the quicktime, itunes, and adobe stuff but there are others you can safely uncheck too. BE CAREFUL, do some Google searches on what each thing actually is, some have funky names but ARE ESSENTIAL!!! If you uncheck the anti-virus you are unprotected, if you uncheck your printer it won't work, etc, etc!! The speed of todays machines, and your i7 in particular, reduces the need for alot of the preloaded stuff! How fast is fast?! It will also give you more 'resources' for other things if they are not loaded at boot time. This is MY OPINION and others WILL feel differently, but this works for me.
RE: If you have some
)
Not exactly a comparable example but still interesting for a giggle:
Windows Supercomputer Breaks Petaflop Barrier
... The problem Microsoft faced with its Top 500 ranking is that the achievement wasn't recognized because the same machine was able to achieve higher speeds using Linux. General manager of Microsoft's technical computing group Bill Hilf said that the benchmarking tests were performed on both Linux and Windows with a resulting 5-percent difference, however Linux came out on top. That said, the Tokyo Institute was only allowed to submit one test to the Top 500 group, and obviously chose the faster of the two...
Happy fast crunchin'!
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
RE: however Linux came out
)
Would it not be more accurate to say that the compiler used for the Linux copy of the application beat out the one used for Windows?
Surely you don't think either OS has anywhere near 5% inherent overhead for this sort of work?
RE: Very interesting... I
)
I'm already running the LTS edition of Kubuntu v10.04, on my Linux PC. I had first read about Ubuntu in PC World and thought I would give it a try. My first *nix type OS was FreeBSD. Although I had it on 2 different PCs, there was a very high learning curve involved in the configuration. I had a hard time understanding what I was doing. That was about 6 years ago.
I went ahead, about 3 years ago, with Ubuntu. The one thing I didn't like about it was the GUI, Gnome if memory serves. I had KDE installed on the FreeBSD PCs and liked it. So, I installed KDE on the Ubuntu PC. Then I discovered Kubuntu which already has KDE installed when installing the OS. Been with it ever since. It is my Linux preference. :)
Martin, I know you're trying to help, and I really appreciate it, really. :) But, wouldn't it be logical to determine that there is nothing wrong with the KVM or anything related to it since the problem is associated to only one OS on a dual-boot PC? When the keyboard and mouse lock up in v10.10 on the i7, I switch to v10.04 on the Linux PC and the keyboard and mouse are working just fine. I switch back to the i7 and they're still locked up. I'm on the v10.04 PC right now and have been for the better part of 2 hours. With more than 3 apps running on v10.10, they lock up. I have had as many as 5 or 6 going at once in the v10.04 without a problem. I've had as many or more going at once in WinXP and no problems.
I can replicate the occurrence right now by starting up 2 more apps, in v10.10, on the i7. But, the i7 has been BOINCing for better than 24 hours and I would like to see what the uptime will be when the WUs are finished. That is my main objective right now. When it's done, I will no longer be running v10.10, so the keyboard / mouse lock up issue is somewhat moot.
I only have one "killer app" and it only comes in Windoze and Mac versions. I did try that app in Wine on Linux. It crashed the computer after about 30 to 45 minutes. I decided not to take that road again.
Thanks Martin! :) The i7 is just over 25 hours and counting. I believe that effectively discounts any possibility of failing hardware. Wouldn't you say? :)
Keep on BOINCing...! :)
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
RE: RE: however Linux
)
Can be.
For example, Linux has a O(0) ("zero-order") scheduler. That is, regardless of the number of jobs waiting to be scheduled, the Linux scheduler will schedule them all always in the same amount of time. If for example the Windows scheduler needs linear time ("O(1)") per number of jobs to do it's scheduling, that could easily cripple performance when scheduling thousands of jobs. Similarly so for other tasks such as process communication, memory management and so on...
For desktop use, with just a few tasks to manage, the most important aspects for kernel performance are reliability and security. The efficiency of how the kernel does things there is not so important. However, in a server or 'supercomputer' environment where very many tasks must be managed in parallel, good design (as with most things) can give a significant performance boost.
Happy crunchin',
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
RE: RE: ... For KVM
)
I've seen a dodgy connector where it would become intermittent only when you pushed one particular switch on a control panel. Pushing another switch remade the contact on the unassociated connector. Talk about dreaming metaphysical connections across the panel! A bit like turning on your house light switch for the lights but also the washing machine springing to life!! Disassembly and reassembly showed a short pin on one connector getting flexed out of it's socket as the panel flexed in a certain way. Flexing the panel another way pushed the troublesome pin back against the edge of the socket to make a good contact...
Try swapping the leads around on the KVM, and swapping ports, to eliminate any one component/connector possibly being the problem.
If consistently repeatable, then that must be a bug of some sort that needs tracing and squashing! I'm sure the kernel devs list will be interested in that one.
Good going there and great if it fixes your problem.
The KVM switch bug should at least be reported if only to warn others of the potential problem.
Good luck!
Happy crunchin',
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
Greetings everyone, ***
)
Greetings everyone,
*** UPDATE ***
Well, BOINC, on the Linux side of the i7, has finished without the problem I was having on the WinXP side of things, save for the random mouse and keyboard lock up discussed previously. On to my clean re-installation of WinXP Pro. Which, by the way, will be a temporary gig until next year when I get Win7 Pro 64 bit. :)
Now, for a disturbing discovery: When I installed Kubuntu v10.10 for the dual-boot test purpose, I found that it was NOT installed where the install app said it was going, where I assumed it was going. It told me it would split my boot drive, drive c:\, in half and place Linux on the second half of the boot drive. WRONG!
I just found out that the partitioning took place on my second drive, where I keep my backup stuff from Windoze, all my personal stuff. And, not only that, it made 2 partitions on the second half, which I assume would be the case under "normal" installation circumstances. So, now I have to reclaim those 2 partitions so that I have access to the FULL drive, through Windoze, and not just half of it. This will delay my clean re-installation of WinXP Pro!
Murphy needs a good slapping upside the head! ;)
@ Martin: I will keep observing the mouse and keyboard problem. Although it is not a problem through Windoze or the Core 2 Duo Linux PC, if I don't see anything, I will try to contact someone of the Kubuntu community to report the problem with v10.10. Although, I'm sure they already know, since I found so much about it on the Internet.
By the way, the i7 with v10.10 ran for 37.5 hours before the next mouse and keyboard lock up, then another 17 hours, for BOINC to finish, without the lock up. And the problem observed when running BOINC in Windoze never appeared. :)
Keep on BOINCing...! :) (the i7 will be within the next 6 hours or so :) )
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
RE: Greetings
)
I wonder if the kvm switch is your Windows problem too, you say it ran just fine for 37.5 hours then again for 17 hours before it locked up under Linux. I wonder if it was locking up under windows but because of the way it locked up you had to reset the machine to make it work again? The way to know is to plug the keyboard and mouse in to the pc directly and let it run that way for as long as it does without crashing. Since you are happiest with Linux right now try that for the next 4 days, then switch to Windows and see how long it runs without crashing. If it makes it 4 days under Linux then I would guess that it fixed that problem, but Windows will be the key test, will it work or crash?
RE: RE: Greetings
)
Greetings Mikey,
I cannot run the test you suggest since Linux no longer exists on the i7. But, the problem I had with the mouse and keyboard locking up in Linux, is now the least of my worries (see update below).
*** UPDATE ***
I have recovered all but 5.334 GB of the space on my second HDD where, for whatever odd reason, Kubuntu v10.10 was installed. Since both my HDDs are 500 GB drives, I'm not concerned with that unused 5 GB.
During my clean re-installation of WinXP Pro, I decided to do the extended format of the boot drive, just to be sure there was no lingering bad code anywhere on it. Formatting took well over 2 hours to complete. WinXP installed without a problem. I installed my various drivers from my install CD that came with the MoBo. All went well, no artifacts appeared on the "cylon" splash screen. Then...
I decided to install my nVIDIA driver(s) from the downloaded update version instead of from the CD that came with the video card. Guess what? Upon reboot, the artifact came back to the "cylon" screen. :( Ok, this tells me that there is a problem somewhere in the driver / software code driving my video card. I tried to roll back the driver to the one WinXP installed and was using only to find out that no driver files were backed up for that purpose. Bummer... :(
Now, here's something a bit odd: It now takes a few minutes for my network icon to show up in the notification area. Before doing all the myriad updates from Micro$oft, it would appear very shortly after my firewall and virus scanner were running. It still shows up after, just a few minutes after, now.
I have not installed BOINC yet and will wait until I can figure out how to fix my "video problem". The problem with uninstalling nVIDIA is that I will no longer have sound, not that that is a really important factor. I just hate seeing the yellow "?"s in Device Manager. ;) I really don't have much use for sound, yet. I fail to understand why nVIDIA would have anything whatsoever to do with sound. I assumed that installing the sound driver(s) from the MoBo CD would suffice, since the sound is an integrated device on the MoBo. Hmmm... Just had a thought: I wonder if I could peek around on my nVIDIA CD and find the files needed for the sound and somehow get them installed. Then again, what's to say that THEY aren't what causes the artifact to show up on the "cylon" splash screen. :/
All in all, though, the i7 seems to be running just fine, despite what I have mentioned above. It boots faster, applications launch faster, etc.
Hmmm... I was just thinking of the past and seem to remember the artifact problem with WinXP Home on the Core 2 Duo as well. It, too, had a video card with nVIDIA technology and driver(s). Same with WinXP Pro on that same PC. Perhaps it is time to switch to another brand of video technology. ATI perhaps?
At least my mouse and keyboard ain't locking up on me now... :)
Keep on BOINCing...! :)
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
RE: ... the "cylon" splash
)
Is WinXP even supported still?
For the windows problems, looks like you're down to checking out for BIOS updates and motherboard drivers.
Quite an adventure!
Good luck,
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
RE: RE: RE: Greetings
)
Are you trying to use the 'latest and greatest' Nvidia drivers? If so drop back a step or 2 or even 3 and see if they work better, sometimes the 'latest and greatest' is not! As for the network icon do the Windows updates, ALL OF THEM, and I thought the 'dot net' stuff was part of that fix. As for your sound card try doing a manual update thru the Device Manager and tell it look in Windows Update when it asks.
Things ALWAYS run faster after a fresh install because none of the little things that we load over the long term are loaded yet. Try to keep things like quicktime, adobe reader, etc, etc, etc from loading prior to you actually needing them. You can do this by editing the Msconfig file, you get there by clicking start, then run and typing msconfig on the line and pressing enter. BE CAREFUL THOUGH. Whatever you change, and ONLY CHANGE things in the Startup section, WILL affect the way the machine runs and IF it boots!!! I ALWAYS uncheck the quicktime, itunes, and adobe stuff but there are others you can safely uncheck too. BE CAREFUL, do some Google searches on what each thing actually is, some have funky names but ARE ESSENTIAL!!! If you uncheck the anti-virus you are unprotected, if you uncheck your printer it won't work, etc, etc!! The speed of todays machines, and your i7 in particular, reduces the need for alot of the preloaded stuff! How fast is fast?! It will also give you more 'resources' for other things if they are not loaded at boot time. This is MY OPINION and others WILL feel differently, but this works for me.