Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by puzzled

  1. I flashed to the earliest available BIOS because there were parts that remained the same when I reflashed & were not over-written. I want to be sure any corruption isn't in the parts that weren't over-written. Now the BIOS will not come up. I've rebooted 5-6 times, saw the red BIOS screen for .5 a second once. Haven't been able to get it to come up again. It now looks like when I do a reset of the jumper for a few minutes the BIOS does its .5 second appearance, & then nothing. I'm going to try it one more time. I just reset the jumper. Waited 5 minutes, swapped positions, the fired it up while hitting delete. It wouldn't show the BIOS screen this time. I'm going to let it sit for 30-60 minutes this time during the reset, before moving the jumper back.

  2. What causes a BIOS to read one thing in the BIOS, & another thing when using CPUZ & A64info? After setting the BIOS, I can't F10 or "Y" out of the BIOS. I need to hit the reset switch or kill the power. When I go back in to the BIOS, my manual settings are still there, but the readings from CPUZ & A64info are different, (after mandatory power kill), after I reboot in to XP. Is the BIOS corrupt?

  3. I was finally able to ship it yesterday. :( I keep some weird hours, so I'm not able to get things done as fast as I'd like sometimes. I kept the package ready to ship in my trunk until I was able to get it to a UPS Store during business hours. The 1st two attempts I missed by a few minutes. On the 3rd shot I made it with 10 minutes to spare. It's finally on its way to Calgary. Shipping was $50. I don't know on what scale this registers as a hassle for me or not. I have 2 of these units, 1 that's worked fine from day 1, & the other that has cost time, money, & customs paperwork to ship back. It would be easier if a call tag could be issued.


  4. Being an absolute newbie, I have no idea what to do with all that. :) I did however try a trial version of Xandros Pro 4.1 yesterday. Drum roll please It immediately recognized the NVIDIA chipset & the RAID array!! So, I was able to install the OS to an array. Now the only thing left is to find out if the video cards are in SLI or not. Any suggestions on how to discover this?

  5. I decided to go with an Abit AM2 board after DFI customer support was non-existent with a 939 board in warranty. I can't remember how many emails I sent them, but I can tell you zero were replied to. If you ever have a problem, just throw the board in the trash. It'll save you a lot of time.

  6. You're right about the installer. It's also the same problem that is present on Gentoo 2007.0. I was looking in to the RAID feature of the installer, & came up with a curious option. It allows you to load the OS on to one HD, & then copy it to the second HD to create the RAID array. I thought that might be the solution. I disconnected the NVIDIA RAID option in the BIOS, & then tried to load the OS to a single HD. The installer crashed again. I then tried to load Gentoo, but the installer on that distro doesn't have the RAID feature. The installer also crashed on that distro. It looks like Anaconda is buggy. I'm going to disconnect one HD, & then do some research in to formatting the other HD manually. Hopefully I can format the one HD, & then the installer will allow me to use the feature to create a RAID array from the first HD.

  7. I managed to figure out how to copy & paste the error report. I have no idea what any of this means.


    Traceback (most recent call last):

    File "/opt/anaconda/usr/lib/anaconda/gui.py", line 950, in handleRenderCallback


    File "/opt/anaconda/usr/lib/anaconda/iw/progress_gui.py", line 250, in renderCallback


    File "/opt/anaconda/usr/lib/anaconda/gui.py", line 867, in nextClicked


    File "/opt/anaconda/usr/lib/anaconda/dispatch.py", line 140, in gotoNext


    File "/opt/anaconda/usr/lib/anaconda/dispatch.py", line 208, in moveStep

    rc = apply(func, self.bindArgs(args))

    File "/opt/anaconda/usr/lib/anaconda/packages.py", line 103, in turnOnFilesystems


    File "/opt/anaconda/usr/lib/anaconda/fsset.py", line 1477, in createLogicalVolumes


    File "/opt/anaconda/usr/lib/anaconda/fsset.py", line 2080, in setupDevice

    raise SystemError, "pvcreate failed for %s" % (volume,)

    SystemError: pvcreate failed for

  8. I'm really surprised to find there isn't a distro that combines what Fedora offers (partitioning for RAID during set up), & what Mint offers (video card usability from CD). Fedora loads the NV SATA driver, & then sees the (2) 80GB HD's as (1) 160 GB HD. It then goes to a scrambled screen on reboot after loading the OS. The video drivers aren't adequate. On the other hand, Mint sees (2) 80 GB HD's, but will only load the OS to one of them. It doesn't do RAID set up, but it can load the proper video drivers after reboot when loading the OS. I wonder when someone will combine both features to CD/DVD?

  9. A brand new hard drive shouldn't have any operating system on it. It sounds like the one you bought was already used by someone else. You can also wipe or scrub the hard drive clean with software, & then load XP on to the clean drive.

  10. That was the best I could do. I tried to save it to floppy, but there's an internal error. I tried to copy, but as soon as you leave that program, it wont paste in to the browser. There's just way too much there to type.

    I guess what frustrates me the most is that with XP it was just F6 & a floppy to set up RAID. It shouldn't be this hard to set up hardware correctly.

    I settled on Mint for the laptop. So far, so good. It loaded the OS & then updated itself. All of the plug-ins for Firefox loaded w/o being asked, or having to be added manually. The only question is will the wireless work? I'm going to try it out in a public WIFI area tonight. If it works, then I would definitely recommend the OS to another newbie.

    I did add Mint to an older PC that I assembled recently from old parts laying about. The OS had no problem with the SATA hard drive or any of the other hardware present. It works like a champ on that system, but again, it's not a RAID set up.

  11. I tried out several more distros in search of one I would be comfortable using on a notebook. Out of curiosity I tried Sabayon on the SLI system with the RAID array. It was the only one in about a dozen attempts that actually went live. It now recognizes both hard drives. I then tried the installer & it has sda & sdb selected as the drives to use for installation.It asked to set up users & passwords. It then tried to install but came up with an error exemption. Any suggestions?

  • Create New...