Quote:

Retry the one you currently have, too, if possible. I'm curious. I find it somewhat unlikely that any recent changes in the sources could have caused the formerly never happening problems you mentioned to suddenly appear.For example I don't think there was any changes at all in sources regarding boot volume detection.

I will download tonights build and let you know what happens.

I will work on getting fedora downloaded and installed by this weekend, hopefully.

We are having a big "push" to close tickets this week and they are working us like dogs.

Quote:

Fedora comes with Python and Bison. If for some reason the user didn't install those, as SU, a user would do "yum install python" (or bison) and the system would do the rest. I wish we had yum version (and a decent package system) for AROS.

Dammy
TeamAROS

Quote:

Try reburning the iso to CD. Or even better, do that with a different/new CD/RW. Just to be sure that it's really some bug/problem.

Quote:

If I dismember correctly, if you do the developer install (or custom and select all the developer stuff), you get everything but python and bison. Those two you gotta install yourself - but that's rather easy.

Quote:

When it locks up, it is completly locked. No mouse, nothing. only a cold boot will correct.

Now here are the real funny things.

When I boot again and select NVidia I get caught in the ...not a bootable disk... loop. Just prior to this I can see a line that says "No ATAPI devices in system" This is strange as the CD-Rom I am booting from is ATAPI. Again I must stress that this build is the only one to fail on this hardware. I have about 4 Aros Cds floating around and they all work. Also, I was going to attempt your suggestion mentioned above to get you some info but I cannot get it to boot at all today. I tried 20 time, I counted. I cannot get it get past that "...no boot device..." today.

Until this build this has never been an issue for me. Also, tried various VESA modes. After hitting <enter>, the screen goes black....and stays that way. It is the same no matter what VESA mode I choose. Again, this is the first time I have had this issue.


Now, I do have a HD with Aros-Max installed. I can boot into that and do whatever if it will help. I can copy files from the CD to the HD if you need me to and do testing that way. If it breaks my Aros-Max install, then so be it.

Quote:

Try opening a shell (From Wanderer menu or by pressing RWIN + W) and start "sys:tools/debug/sashimi" in there. When it locks up is there something that gets output in the shell window by sashimi?

Do the lockups also happen when using VESA driver?

I downloaded todays nightly native build. No errors on NVidia and the preffs for Nivdia are back!!! YEEEE!!! HAAAAA!!!!

However, the whole thing locks up on me about 30 seconds after Wanderer starts. No matter what I am doing. Also, a few times it would get stuck in the ....no bootable disk... loop. Even though the "floppy" is turned off in Bios. This has not been a problem on this box before today.

If i use Fedoa. Does it come with all of that stuff?

Fedora Core is also available via bittorrent, which is what I always recommend. FTP is so unreliable.

Here's the wiki page for setting up development on Ubuntu:

http://www.ubuntulinux.org/wiki/DevelopersDocumentation

From the AROS compiling page, here's what you need:
The following software is required for compiling AROS:

* GCC 3.2.2+
* GNU Binutils
* GNU Make
* GNU AWK (GAWK) - other awks may also be suitable
* Python 2.2.1+
* Bison
* pngtopnm and ppmtoilbm (part of the netpbm package)
* Autoconf
* Automake
* Common utilities like cp, mv, sort, uniq, head, ...