btlds

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

From: Bela Lubkin <belal@caldera.com>
Subject: Re: booting restored kernel on new hardware, am I screwed or what?
Date: Tue, 6 Nov 2001 21:39:30 GMT
References: <9s8s2j$ko4$1@slb3.atl.mindspring.net> <MyXF7.143392$RG4.1322445967@newssvr10.news.prodigy.com> <9s9jvs$shf$1@slb6.atl.mindspring.net> 

John H wrote:

> OpenServer 5.0.6, BackupoEdge 01.01.08
> 
> When creating the boot/root disk set, I ran RecoverEdge and let it do it's
> thing.  I didn't do anything other than insert the disk(s) when it told me
> to.
> 
> Tryed btld from the command prompt and I get a out of memory error (huh? I
> got 98MB in here, mebbe I'll have to spec that in the boot string as well)

The program that does the boot-time linking of BTLDs is a small-model
8086 program.  It has some very limited knowledge of 32-bit address
space for purposes of copying the actual kernel code up there.  It does
the _linking_ in 8086 mode.  Specifically, the kernel and BTLD objects'
symbol tables get loaded into the low 1MB of memory.  It's quite easy
for it to run out of space.

Check BIOS setup: many modern machines have settings which control
whether 512KB or 640KB of the low 1MB are available.  You won't be able
to BTLD anything if it's set to 512KB.  At 640KB, you at least have a
chance.

> I've gotten the system booted from a kernel build on an ide system, but I
> need to now try to figure out how to tell my system the root disk is ide, not
> ida, and then I should be able to relink a new kernel and boot and be happy
> again.  Until then... I'm still muttering ...

Rather than all this, what you might want to do is start a new, fresh
install on the replacement machine -- starting from the OS distribution
CD.  (Or possibly from SmartStart if these are Compaqs, like I seem to
remember from the previous messages.)  Anyway, using whatever is the
correct procedure for the replacement machine, do a new install.  Then
restore your data from the old system, being careful not to restore the
OS portions.  Finally, if necessary, restore the OS portions into a
subdirectory.  You can use the restored old OS as a reference for things
like kernel parameters you had changed.

>Bela<
 

Take Control of Upgrading to Snow Leopard

Take Control of Exploring & Customizing Snow Leopard

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.