Congratz, and welcome!  ;)

Google for FreeBSD BTX boot scsi shows a history of people having trouble doing a FreeBSD install with SCSI drives in the system and the problem appears to be in BTX. I suggest you disable your SCSI controller, add an IDE drive to the system and attempt to install onto the IDE drive.

When I boot the pfSense install CD the console output does pause at that point for a few seconds then carries on. I suggest if it pauses more than (say) 30 seconds you give us a bit more information about what you are trying to do so we have something more specific to work with: What version of pfSense? Is the CD drive an "internal" (IDE) drive or external (USB?) What type of system: CPU, memory, drives, NICs?

Thanks for that. I'll try one of your suggestions tonight. Just for your, or anyone else reading's, information. The machine is an AMD Athlon XP 3200+ on an ASUS A7N8-E Deluxe ACPI BIOS Rev 1013 (Nvidia nforce). With Phoenix Award BIOS v6.00PG.

@cheesyboofs: Hi Chris, Great stuff! You say you where able to test 1.2.1 with spamd, where you able to confirm it working on 1.2.1 before you went back to 1.2, because I'm having a little trouble. http://forum.pfsense.org/index.php/topic,11044.0.html Out of all the pfSense features the spamd plug-in seems to be one of the simplest to configure and I'm not exactly a moron but would you give my post a quick perusal and see if you can spot anything obvious. Cheers Never got far enough to send traffic through it to be honest, so, mine could have had the same issue, it appeared everythiing was right, but again, didn't get to send traffic through it.. sorry!

As every other post on the issue of release dates has said - it'll be released when it's released ;) As far as whether or not it is suitable for use, only you can really decide - read the forum and see if the problems people are reporting are, for you, showstoppers.

Why dont you install the full version? To avoid death of the CF due to repeted writes, you "could" install the full version and then change it into the embedded. This is not officially supported, but seems to work quite well for a number of users. –> http://forum.pfsense.org/index.php/topic,6469.0.html howto --> http://devwiki.pfsense.org/FullInstallOnWRAP

I don't know the internal working of pfSense in this regard so the following suggestion might be way off the mark. WAN and LAN interfaces seem to have a special meaning in pfSense and possibly some special "hidden" firewall rules. Can you add  or configure a third interface to this box? It will default name to opt1. Then bridge opt1 and LAN and leave WAN unconnected (so connect your previous WAN to what you now call OPT1). Probably not optimal but you wanted something in a hurry. I have a wireless LAN configured this way and it seems to have been working fine for a couple of months.

Found the problem. These cisco devices have a simm card in them that it tries to boot off. Pulled it out and now all is good.

so it is possible to make a clustering . sounds nice  ;D

Nice, 1.2.1 detected all of them

I agree that it works. I'm just pointing out that you lose the security gained from separate subnets because clients can easily roam between them. We do it for certain pieces of the campus; however, when you do it correctly with VLANs, it creates more security and network segmentation possibilities for hosts based on their purpose. If a VLAN capable switch isn't available, just be aware of the security concerns and aggregation of the broadcast domains.

@AudiAddict: The snort package is unstable and has been removed from the package list. Check the package forum. Many thanks for that. I assumed my problem was to do with the upgrade and not with Snort itself! I assume the problem is that pfSense tried to download Snort (as it's in the config) but couldn't so it's half there and half not so to speak. I'll follow the problems with Snort in the package forum.

I believe there is somewhere a thread around with a description how you can turn a full install into some kind of embedded. If you use the search-function of the forum http://forum.pfsense.org/index.php?action=search and use the keywords "embedded full" you'll find this thread: http://forum.pfsense.org/index.php/topic,6840.0.html (hint: repeated use of the search function will lead to results ;) )

I thought I had written the iso with nero, actualy it was poweriso which i used. Switched to NERO and burned another disc at disc-at-once joilet96 and that did the trick!  :D TY

Thanks!

Its possible you may need to boot the pfSense kernel without ACPI. If necessary, try booting the livecd, selecting the ACPI off kernel, and restoring a saved config file. I got bitten by this a few days ago. monowall 1.2 worked, monowall 1.3* (b7, b13) didnt get traffic in or out of either ethernet card, pfSense 1.2 was the same as monowall 1.3* until I booted ACPI off, then all was fine again. & Now if I just knew how to install pfSense to hard drive with the ACPI off kernel… &

Sorry man, you're out of luck! pfSense is FreeBSD and NOT Linux. Repeat after me: FreeBSD is NOT Linux. OK, your turn now!  2, 3, 4, louder, I can't hear you! pfSense is a complete distribution like your FC. You cannot run CentOS on top of that either. Well, except for a VM, but that's a different story…

new switch  ??? ? nobody will pay  :P i think i have to separate my Wans from switch, and of course climb up my tower to move the wireless closer to the Pfsense. and there will be nothing at the top of tower.  :-X :D thanx guys.