On Dec 17, 2005, at 1:16 PM, Matthew Pierce wrote:

Have you tried setting the boot partition to (0,0).  Maybe it's
possible the Windows stuck its boot loader into the front of that
partition?

If that doesn't work, I would second the proposal to "repair" the
windows installation.  It shouldn't destroy it...you'll just bring the
OS back to it's original, unpatched state and hopefully restore
whatever might be missing/corrupted.  Your files and partitions should
all remain intact.

_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/

Well non of the boot partitions that I specified worked. I ended up just doing a total re-install of windows on my machine. Of course doing that, I lost my boot loader.

I decided to then try to do a repair of the linux system and the boot loader but the cd's I have don't appear to be working anymore. Maybe scratched or whatever the case may be. I remember that I downloaded the "unofficial" 4.2 cd's a week ago, so I decided to use those and run the upgrade procedure (not sure if that was wise).

So I run the upgrade procedure and low and behold I have my boot loader back and all seems to be well. Of course this now introduced a problem. Now that the kernel was upgraded, my wireless card (ndiswrapper) stopped working. Now I am trying to get that back on track and then I will be home free. I have had to update to the absolute latest ndiswrapper rpm and then try to get my wireless working but nothing has failed. I keep getting the check cable error. I have tried deleting/recreating my network profiles but no luck. I have tried uninstalling/installing the network devices but still no luck.

Can anyone think of something I maybe missing?

_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/

Reply via email to