i did exactly what u said but windows repair rand for hours and didnt do anything. i had to manually power down the pc.
so besides that. i installed win7 again, this time from external optical drive (taking out my external hdd) into my raid array. now the installation made a 100mb partion and stored bcd there.... is this because of raid?
any how computer runs fine, without any problems but if u guys think this 100mb partition will be a problem let me know
The 100mb Sys Reserved partition puts the Repair console on the F8 Advanced Boot Tools menu. I would keep it for that reason.
On a large drive you eventually won't even notice it. Since your SSDs are only 60gb in size the recommendation would have been to first partition and format the drive separately using something other then the drive tools the Windows installer uses.
Even without that the startup repair tool will appear if 7 sees any startup problems. That was found to be the case even with the beta and RC builds being an automated process to bring that up with hard shutdowns like a program locking things up solid forcing a hard boot for example.
You typically won't see that option in the F8 options unless a forced restart is seen as a rule. The "Last configuration known to work" option as the Startup Repair are then seen when the F8 comes up on it's own.
i see.
well size wont be an issue. the reason i went with this raid set up is because i use 3d biochem modeling programs that constantly works with large files. with this raid set up the process is alot painless.
i extracted my external hdd and installed within chasis and formatted. so will use it constantly now.
well thanks alot for the help guys.
It's hard to give up ImgBurn since it never fails on intact ISO, but the Win7 built-in burner is pretty good too. It doesn't fall apart with the slightest challenge as Windows burners have in the past.
Apparently you haven't been running the more recent versions. I'm alreadt well famiiar with the program and find it can problematic at times on the 64bit side. When going to click the burn button surprize! A command prompt window opens and everything freezes up.
One time incident? On the beta, later on the 64 RC installs, and even on the retail 64bit on more then one system even seeing the same thing. Never any problem on the 32bit however.
The other program on the other hand can be used for more then just burning iso images and has been reliable even before Vista was released for use on XP as well as now found reliable on the 64bit 7. That and always end up being the dependable ones.
NightHawk,
I don't know what went wrong on your installation but ImgBurn works very well on 32 bit and 64 bit systems.
ImgBurn supports all the Microsoft Windows OS's - Windows 95, Windows 98, Windows Me, Windows NT4, Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 2008 and Windows 7 (including all the 64-bit versions).
That's from the ImgBurn site. I'm sure they would be interested in hearing of your experiences.
Last edited by karlsnooks; 15 Sep 2010 at 18:21. Reason: add statement from imgburn site
I used version 2.4.2.0 for a long time and in July I started using 2.5.1.0 and I just downloaded 2.5.2.0 but I intent to continue to use 2.5.1.0 for quite a while as that's the one I have added now but when I reinstall I'll start using the new version; I always open it using "Run-As" to burn an ISO and have never had any issue of any kind either creating or burning an ISO with it.
I guess we'll just have to agree to disagree because this is the last reply I intend to make on this subject.
Quote
