Prev: Crimpable Rj12 female
Next: Picture tube degaussing
From: Jeffrey D Angus on 25 Apr 2010 16:42 Meat Plow wrote: > On Sun, 25 Apr 2010 14:57:49 -0500, Jeffrey D Angus > <jangus(a)suddenlink.net>wrote: > >> Meat Plow wrote: >>> On Sun, 25 Apr 2010 04:42:58 -0400, Jamie >>> <jamie_ka1lpa_not_valid_after_ka1lpa_(a)charter.net>wrote: >>> >>>> some Laptops have a partition on the HD that has special set up >>>> software at boot time to configure the proprietary onboard chips.. >>>> This also could be an issue.. >>> What laptop(s) would have this feature? >> Compaq, they were nortorious for having a special partition they would >> fail to boot if they didn't find. > > I've never owned a Compaq laptop but working in the industry when > Compaq was the workstation of choice I would have thought I'd read > about it somewhere. This must have been really proprietary as I've > never heard of a chipset needing to load code from a fixed drive > during boot. Can you give me an example of a model number and year > and what operating system? Not that I don't believe you I'm just a bit > taken back that onboard chips could be so proprietary that they > couldn't be produced with their own non-volitile embedded instruction > sets. > The Compaq Presario series comes to mind. They had a special 1-2 meg partition on the hard drive that the bios looked for and not finding, would hang the system. "OS NOT FOUND" I found out the hard way, loading SCO Unix on one, going through the entire ordeal of loading the operating system (and mistaking wiping the service partition, then rebooting and finding I had to (a) replace the service partition and reload the service software and (b) start from scratch again with SCO Unix install. Jeff -- �Egotism is the anesthetic that dulls the pain of stupidity.� Frank Leahy, Head coach, Notre Dame 1941-1954 http://www.stay-connect.com
From: Baron on 25 Apr 2010 17:06 Jeffrey D Angus Inscribed thus: > Meat Plow wrote: >> On Sun, 25 Apr 2010 14:57:49 -0500, Jeffrey D Angus >> <jangus(a)suddenlink.net>wrote: >> >>> Meat Plow wrote: >>>> On Sun, 25 Apr 2010 04:42:58 -0400, Jamie >>>> <jamie_ka1lpa_not_valid_after_ka1lpa_(a)charter.net>wrote: >>>> >>>>> some Laptops have a partition on the HD that has special set >>>>> up >>>>> software at boot time to configure the proprietary onboard chips.. >>>>> This also could be an issue.. >>>> What laptop(s) would have this feature? >>> Compaq, they were nortorious for having a special partition they >>> would fail to boot if they didn't find. >> >> I've never owned a Compaq laptop but working in the industry when >> Compaq was the workstation of choice I would have thought I'd read >> about it somewhere. This must have been really proprietary as I've >> never heard of a chipset needing to load code from a fixed drive >> during boot. Can you give me an example of a model number and year >> and what operating system? Not that I don't believe you I'm just a >> bit taken back that onboard chips could be so proprietary that they >> couldn't be produced with their own non-volitile embedded instruction >> sets. >> > > The Compaq Presario series comes to mind. They had a special 1-2 meg > partition on the hard drive that the bios looked for and not finding, > would hang the system. "OS NOT FOUND" > > I found out the hard way, loading SCO Unix on one, going through the > entire ordeal of loading the operating system (and mistaking wiping > the service partition, then rebooting and finding I had to (a) replace > the service partition and reload the service software and (b) start > from scratch again with SCO Unix install. > > Jeff > I remember those ! Caused all sorts of mayhem. If I recall the trick was to wipe the MBR and sys the drive from a floppy boot disk. -- Best Regards: Baron.
From: Jamie on 26 Apr 2010 09:55 Meat Plow wrote: > On Sun, 25 Apr 2010 04:42:58 -0400, Jamie > <jamie_ka1lpa_not_valid_after_ka1lpa_(a)charter.net>wrote: > > >> some Laptops have a partition on the HD that has special set up >>software at boot time to configure the proprietary onboard chips.. >> This also could be an issue.. > > > What laptop(s) would have this feature? Acers off the top of my head. Maybe not the current ones.. But I had to correct an older one that did this. The owner installed a newer OS, The process reported that the current partition was not the primary one and asked if he wish to make the install the primary one etc... etc.. And he did..................... etc All was going just fine until it was time to reboot, when he did, windows could not find the CD rom, any longer. To fix it, we move the HD to a USB external drive cable I have on another PC and used the recover CD that restored the HD back to original. Put it back in the laptop and then install the new OS over the existing one. That worked out fine.. Take it for what you want, if you have been around long enough, this isn't a new technique, things like this was done back in the hay day to configure your HD, the device settings were on the HD platter.
From: Jamie on 26 Apr 2010 09:57 Jeffrey D Angus wrote: > Meat Plow wrote: > >> On Sun, 25 Apr 2010 14:57:49 -0500, Jeffrey D Angus >> <jangus(a)suddenlink.net>wrote: >> >>> Meat Plow wrote: >>> >>>> On Sun, 25 Apr 2010 04:42:58 -0400, Jamie >>>> <jamie_ka1lpa_not_valid_after_ka1lpa_(a)charter.net>wrote: >>>> >>>>> some Laptops have a partition on the HD that has special set up >>>>> software at boot time to configure the proprietary onboard chips.. >>>>> This also could be an issue.. >>>> >>>> What laptop(s) would have this feature? >>> >>> Compaq, they were nortorious for having a special partition they >>> would fail to boot if they didn't find. >> >> >> I've never owned a Compaq laptop but working in the industry when >> Compaq was the workstation of choice I would have thought I'd read >> about it somewhere. This must have been really proprietary as I've >> never heard of a chipset needing to load code from a fixed drive >> during boot. Can you give me an example of a model number and year >> and what operating system? Not that I don't believe you I'm just a bit >> taken back that onboard chips could be so proprietary that they >> couldn't be produced with their own non-volitile embedded instruction >> sets. >> > > The Compaq Presario series comes to mind. They had a special 1-2 meg > partition on the hard drive that the bios looked for and not finding, > would hang the system. "OS NOT FOUND" > > I found out the hard way, loading SCO Unix on one, going through the > entire ordeal of loading the operating system (and mistaking wiping > the service partition, then rebooting and finding I had to (a) replace > the service partition and reload the service software and (b) start > from scratch again with SCO Unix install. > > Jeff > > Fun, isn't it :)
From: Jamie on 26 Apr 2010 10:11
Meat Plow wrote: > On Sun, 25 Apr 2010 15:42:49 -0500, Jeffrey D Angus > <jangus(a)suddenlink.net>wrote: > > >>Meat Plow wrote: >> >>>On Sun, 25 Apr 2010 14:57:49 -0500, Jeffrey D Angus >>><jangus(a)suddenlink.net>wrote: >>> >>> >>>>Meat Plow wrote: >>>> >>>>>On Sun, 25 Apr 2010 04:42:58 -0400, Jamie >>>>><jamie_ka1lpa_not_valid_after_ka1lpa_(a)charter.net>wrote: >>>>> >>>>> >>>>>> some Laptops have a partition on the HD that has special set up >>>>>>software at boot time to configure the proprietary onboard chips.. >>>>>> This also could be an issue.. >>>>> >>>>>What laptop(s) would have this feature? >>>> >>>>Compaq, they were nortorious for having a special partition they would >>>>fail to boot if they didn't find. >>> >>>I've never owned a Compaq laptop but working in the industry when >>>Compaq was the workstation of choice I would have thought I'd read >>>about it somewhere. This must have been really proprietary as I've >>>never heard of a chipset needing to load code from a fixed drive >>>during boot. Can you give me an example of a model number and year >>>and what operating system? Not that I don't believe you I'm just a bit >>>taken back that onboard chips could be so proprietary that they >>>couldn't be produced with their own non-volitile embedded instruction >>>sets. >>> >> >>The Compaq Presario series comes to mind. They had a special 1-2 meg >>partition on the hard drive that the bios looked for and not finding, >>would hang the system. "OS NOT FOUND" >> >>I found out the hard way, loading SCO Unix on one, going through the >>entire ordeal of loading the operating system (and mistaking wiping >>the service partition, then rebooting and finding I had to (a) replace >>the service partition and reload the service software and (b) start > >>from scratch again with SCO Unix install. > > Wel that's really odd. OS not found usually means the BIOS can't find > the MBR or the bootloader can't find the partition, the directory of > executables including the OS kernel as described in the boot.ini file > of a Windows OS. I'll have to do some research and find out just what > chips are uploaded code from this 'service' partition just to satisfy > my curiosity. A lot of these machines had/have simple controllers. Many of them really don't function much, or not at all. The firmware is uploaded from that partition or service boot that redirects the boot process, which is a hard one to fix if you're trying to upgrade.. The devices come alive when the firmware is uploaded and executed. This is kind of a neat way of doing things because, you can control the firmware release depending on the region, regulations etc... For example, lets say we program the CD rom controller to not allow you to read some security CD's or regions that don't match yours, Network access depending on where you are, this way, they don't need different hardware PC's. All they need to do is put in the correct HD that fits the location of where it's going. It's also a good way I guess to perform firmware updates by simply updating the service section and doing a cold boot. That's when the fun starts if the update didn't go well :) |