Alright, I have to say it out loud that I haven’t had so much fun working on an IDE after Visual Studio 6. Flash Develop is definitely one of the best IDEs for professional flash programming out there. I’ve worked with Flex/Flash Builder, FDT and IDEAj but after spending some time with these IDEs, I believe they’re bloated with over-engineered features that don’t belong in the Flash environment. If there is anything that Flash Develop lacks against these IDEs, it is better Refactor support.

Anyhow, this post is not about which IDE is better. I’ve worked with Flash Develop for a long time now and there are some plugins that I’ve used to increase my productive time. These plugins make your development faster and much more robust. I thought I should make a log of these plugins and if they would help anyone using Flash Develop in their routine development.

Name: Ant Plugin
URL: http://code.google.com/p/fd-ant-plugin/

Anybody working on projects with multiple targets or components cannot avoid the power of ANT. ANT is the definite tool for automating builds and continuous integration. This plugin simplifies the process of integrating ANT in your project. You can drag drop your build targets into your project panel and build targets selectively. Highly recommended.

Name: NME Target
URL: http://www.flashdevelop.org/community/viewtopic.php?f=4&t=9309

Haxe is amazingly simple to port your flash environment to and anyone coming from the flash world can pick it up fast. What makes it even better is the fact that FlashDevelop is the best IDE to develop in Haxe. If you’re working on an NME project,this plugin will help you immensely. The plugin will put multiple build targets to your FD toolbar. You can select a target like Flash, HTML5 or Android on the fly. The toolbar is customizable as well.

Name: Project Export
URL: http://www.flashdevelop.org/community/viewtopic.php?f=4&t=4641

This plugin was one of the first Flash Develop 4 plugins I used and before I found the ANT plugin. It helps you with many regular tasks on any project. For example: Create Documentation,export your deployment directory etc. If you’re not ANT savvy, this plugin can ease some of those tasks.

Name: Export SWC
URL: http://sourceforge.net/projects/exportswc/

Building SWCs is one of the core components of Flash development. You do not need the FlashIDE for building an SWC anymore. This plugin makes it very easy to build an SWC from you current project.

Name: Quick Navigate and Navigation bar
URL: http://code.google.com/p/fd-quick-navigate-plugin/

URL:https://github.com/JoeRobich/fd-navigationbar

I really missed the quick navigation of Visual Studio and these two plugins make it a snap to find and navigate through your code. The quick navigation dialog can find code, variables through string matching. The navigation bar adds visual studio like class and function/property dropdowns under your Flash Develop toolbar. Really handy!!

Name: SlimTimer
URL: http://code.google.com/p/fd3slimtimer/

I always wanted to track time on my development environment for clients or my job. This plugins integrates with the SlimTimer service and logs your projects automatically. It’s integrated really well and does not get in your way. Highly recommended if you want to track your time and it is for FREE!!.

Apart from some plugins that I use for Flash Develop, there are some snippets that help me with certain requirements. So here goes:

Name: SVN Revision info generation
URL: http://www.blixtsystems.com/2008/05/svn-version-control-in-flashdevelop-projects/

Name: Build Organization
cmd.exe /c “xcopy /Y $(OutputDir)\$(OutputName) $(OutputDir)\$(BuildConfig)\”

Just put the above command in your post build field and it should automatically move your debug and release swfs in respective folders. Very handy!!

Let me know if you guys know of any other useful plugins or scripts.

The Sandy Bridge platform has seen quite a lot of down hill turns in his short life time. First the Cougar Point issue, then a series of Processor and Motherboard delays, and the P67/Z68 Fiasco and the failed attempt to keep the platform up to date with bios and driver releases. Of course, the third party manufacturers like ASUS, Gigabyte and MSI have their share of bad support for the platform as well but it’s mainly Intel that’s to blame. People have faced so many issues on the Sandy Bridge platform that it feels flaky at best. I just wonder my PC would shutdown any moment. It’s happened to me and a lot of other people.

Apart from many of the “bigger” and “widespread” issues with the Sandy Platform, like the one I blogged about some time ago, there has been another issue that’s been plaguing the users of Sandy Motherboards. The issue has something to do with no POST on cold boot and the following error codes:

0C-0D - Reserved for future AMI SEC Error codes

62 - Installation of the PCH Runtime Services

94 - PCI Bus Enumeration has started

D2 - PCH Initialization Error

There is no detailed information about these error codes in the manuals or the AMI website. I picked those definitions up from my P67 manual. I believe it should be the same for all Sandy Bridge motherboards with EFI bioses. Let me go through the error for reminder’s sake:

On a cold boot, your monitor will not show any display and your motherboard won’t POST. If you have the internal speaker attached to your motherboard, you will hear beeps about those error codes as well. However, the error is specifically noticeable when you look at your motherboard physically. The following signs should tell you what’s going on

1. Your VGA LED next to your PCIExpress x 16 slot is constantly lit.

2. If your motherboard has Q Code or Debug Code LEDs on it, you will see it either stuck at 0D, 62 or 94 or in rare cases at D2.

3. Your Motherboard boot LEDs might be constantly lit as well.

If you’ve seen any of the above symptoms, you may have scoured the internet for a solution. The issue happens to be more frequent in ASUS motherboards. People on the internet have exchanged their motherboards in hopes to kill the error, and some have been successful after an exchange but others have been unlucky. Some have pointed out that it’s because the PCI Bridge is dead/corrupted or damaged.

Some people have shifted from their primary PciExpress x 16 slots to their secondary slots x8 and the issue seems to go away. However, it has returned for some in that case as well. This is very frustrating if you’ve hit the issue.

Somehow, I was not satisfied with the sudden notion that the hardware went bad just like that. So, I searched myself and found all the same results and then I turned back to the motherboard manual and datasheets from the manufacturers themselves. I found this:

The Image tells us that the PCIExpress x 16 slot shares IRQs with other components on the motherboard. This sounds exactly like where it’s going. An IRQ conflict/sharing issue. I went to the ASUS motherboard pages to verify if the components shared bandwidth as well and I found this for the P8P67/P8Z68 Pro:

 *1: The PCIe x16_3 slot shares bandwidth with PCIe x1_1 slot, PCIe x1_2 slot, USB3_34 and ESATA12. The PCIe x16_3 runs at x1 mode by default for system resource optimization.(PCIe x1_2 will be disabled.)

The above note is only mentioned in the P8P67 Pro and lower models and the Deluxe/Extreme models do not have this note displayed. I can’t say if it is only for marketing but perhaps the upper models share bandwidth with the components as well.

Why, you ask? Because I solved the issue by disconnecting the USB3_34 Front Panel slots that share bandwidth with the PCIExpress x 16 slot. I have disconnected, reconnected, changed Graphic cards and slots to test my motherboard and it keeps working with the above solution.

This is strange and is possibly a fault in the BIOS. I recommend you to not upgrade to the Beta bioses posted by ASUS and other manufacturers. These bioses might damage your system because they threw the QA garbage over to the customers.

I’d be glad to know if this works out for any of you. It’s a detailed post, I know but I like to detail what caused the issue in the first place.

I have been messing around with my new Sandy Setup and this is one of the pesky issues that have annoyed me recently. I googled this and found that there’s a heap of users complaining about it on the internet. ASUS, ASRock, Gigabyte etc are all affected by it. This probably means that it has something to do with the chipset and not the board manufacturer. This is not an Overclocking tutorial, this is a fix only.

If you’ve reached this post then you already know what the issue is but if you don’t, well, here’s some detail on it.

P67 Motherboards tend to Double Boot on every cold start once you mess around with the Overclock settings. This could be any settings, as far as I’ve seen. If you change the CPU OC profiles or the DRAM OC profiles. One of them will cause the double boot to occur. Some people are a bit unlucky to have triple boots and it is definitely annoying as hell.

Now, I won’t go into details of what solutions others have provided for this problem. But I found that, it happens when my CPU BCLK is nudged over “100“. This is caused by using ASUS’s AI Suite II‘s built in Overclock Tuner or an Overclock profile. For my case, it was always nudged to “103“.

The DRAM frequency is also affected by the BCLK and you’ll see strange numbers as “1648” instead of “1600” or “1800” in the Bios profile. This is exactly what causes the Double and Triple boots. Well, at least for me.

Here’s teh solution that I’ve tried 3-4 times after messing around with the settings again and again and it works. Before you start, here’s a couple of things, you might wanna take note of.

• If your system is Overclocked and is stable, notice all the settings in the bios. If you’ve used an overclocking suite, like the one provided by ASUS, then you should note what settings it made in the bios. DRAM timings, CPU settings, Voltage etc.
• Upgrade your bios if you haven’t already. Should get this out of the way as well.

Let’s move on to the real deal:

1. Go into your bios and load optimized defaults. This should reset the system to factory defaults.
   
   
2. Save and reset system and then shutdown the system.
3. Now reset your CMOS. You’ll need to consult your Motherboard’s Manual for that. Mine was at the back panel (ASUS).
4. Once you’re done with that, start up your system and go into your bios.
5. Find settings for “Onboard Devices” and look for “JMicron and Marvell” etc. You should see they have options under them called “Display OPROM” or “Display OptionROM in Boot“. Just disable those. All of them. You don’t need them for now.
   
   
6. Move on to your CPU Overclock page and start entering values for overclocking. DO NOT CHANGE ANY OPTION FOR DRAM RIGHT NOW.
7. While you’re entering OC settings, Make sure you never change the BCLK, Keep it “100″. That’ the gist of it.
8. The Turbo or CPU Multiplier should be 45-50, depending on what processor you use and how much your system can Overclock.
9. Once you’ve completely entered all of the Overclock settings. Save settings in bios and reset.

If your system is running fine, test your Overclocks. You can then return to the bios and change your DRAM profile. Notice that it should be a square number now. 1600, 1800, 2000, 2100 etc. Pick whatever you feel is suitable for you RAM. Enter the RAM timings, voltage etc and save settings in the bios.

Shutdown or restart the system and you shouldn’t have any more double or triple boots. Let me know if this works for you people or not as well.