Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
BCM50 R6 HDD
- Thread starter Bucky101
- Start date
Firebird Scrambler
Systems Engineer
I think it's because the BIOS was changed during the upgrade from release 3 to 5 or 6.
All the best
Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK
If it's working, then leave it alone!.
All the best
Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK
If it's working, then leave it alone!.
It might also be looking for the upgrade keycode from R3 to R5/6
Brian Cox
Georgia Telephone
Brian Cox
Georgia Telephone
- Thread starter
- #4
The "BIOS" stored on the BCM50 main board is updated when you upgrade a system from BCM50 release 3 to release 5/6. There is no difference between 5 and 6.
There should be no problems with booting newer image on older system. You won't be able to boot older image (e.g., release 3) on a newer system (release 5/6).
Your problem in this case is not the image itself - it is the device (hard drive) that you used. Most likely the drive you have is recognized by the R6 system, but not recognized by the R3 system (its "BIOS"). BTW - I just connected a drive with the R6 image to my BCM50 R1 system - it booted without problems.
I'd like to add a word of caution if you consider bypassing the R3->R6 upgrade by changing the drive to R6 and getting updated keycodes. The upgrade process (besides the logical update of the software on the hard drive)
a) updates the "BIOS" code on your BCM50
b) makes configuration changes that are required for certain R6 features (e.g., booting to the safe OS)
You'd skip these two steps. The result would be a BCM50 system that runs R6 image with R3 BIOS and R3 startup configuration. This combination is fine for a normal use, but the system may not behave as designed if you want to do some "low level management tasks".
There should be no problems with booting newer image on older system. You won't be able to boot older image (e.g., release 3) on a newer system (release 5/6).
Your problem in this case is not the image itself - it is the device (hard drive) that you used. Most likely the drive you have is recognized by the R6 system, but not recognized by the R3 system (its "BIOS"). BTW - I just connected a drive with the R6 image to my BCM50 R1 system - it booted without problems.
I'd like to add a word of caution if you consider bypassing the R3->R6 upgrade by changing the drive to R6 and getting updated keycodes. The upgrade process (besides the logical update of the software on the hard drive)
a) updates the "BIOS" code on your BCM50
b) makes configuration changes that are required for certain R6 features (e.g., booting to the safe OS)
You'd skip these two steps. The result would be a BCM50 system that runs R6 image with R3 BIOS and R3 startup configuration. This combination is fine for a normal use, but the system may not behave as designed if you want to do some "low level management tasks".
- Status
Similar threads
- Locked
- Question
- Question