Please attach the complete /tmp/anaconda-tb-* file to this bug report.  Without it, we cannot debug this problem.

Can't. read only FS.

Also when I plug in external USB or other medium to copy the file to, i can not access it as the base install kernel doesnt seem to be able to support it?

You can scp the file to another machine, or you can attach a device and mount it manually.  The kernel absolutely does support USB devices.

I found out this is because the textmode installer offers no opportunity to enter proxy server information for a network install.

Also, the error messages produced after the sudden death of the installation process offer no glimmer of insight as to the nature of the error.

The way I found this out was to lug a huge server home, and I noticed it installed fine on my home DSL connection.

I took it back to work, where our networks have no direct internet connectivity by design, and everything must use a proxy server. It died, same death..

All of this time I was waiting for an opportunity to tell the installer about:
1) my network interface (static or dhcp)
2) IP addressing (if not dhcp)
3) change any of the options for the NIC
4) other network variables (such as proxy settings)

But, no, I realized at home that it just simply expects "raw, unfiltered internet or dammit I'm not goonna work."

I was able to use a test cable modem we have in our datacenter to install the servers with base packages, then reboot them onto our secure networks. They did fine on DHCP, and after exporting env vars, yum had no problems installing things from there.

In 2013, I guess I just expected more than I received in a textmode linux installer. 

Somehow we focused on games and 3D instead of... um.. getting the OS working.

The text mode interface is not the primary installation interface.  It's not what we spend all our time on.  You can try the graphical installer, or you can try VNC if you've got another computer available.  The problem here is that I've asked for data on the actual failure, and not gotten anything.  Without that information, I can't do any debugging of your problem to even know where to begin with what is going on.  Sorry.

I am copying the data now to a USB stick(the first one I tried was an invalid format)

I will add the data soon

This server has no graphics adapter so X is a failboat.
This network has no usability for VNC due to security, so textmode is the way to go.

There is no /tmp/anaconda-tb-* 
There is a /tmp/anaconda.log

would you like that?

Created attachment 741687 [details]
anaconda.log

Created attachment 741688 [details]
dmesg > /mnt/(mountpoint)/dmesg.txt output

Created attachment 741689 [details]
X log

Created attachment 741690 [details]
ifcfg.log

Created attachment 741691 [details]
what it looks like when it dies

Created attachment 741693 [details]
The HP server stack I am installing at our secondary location

Duplicate stack has been installed at our primary location

Created attachment 741694 [details]
what I believe would help

Screenshot from the ubuntu installer. It asks for proxy settings.

Also, if you get something wrong, it kindly offers an informative error message, asks if you would like to retry (fedora's only option is the three-finger salute, which takes forever on an HP 4G proliant to boot!). It doesn't puke python all over the screen.

This works, and I don't have to switch from our secure networks with proxy internet access to a damn cable modem to install the server.

this couldn't have been that difficult to implement. 

I last used Fedora 7 as a desktop and abandoned it years ago. I know the textmode installer then had to have been at least this decent.

*** This bug has been marked as a duplicate of bug 906031 ***