View Full Version : Unhack Tivo - Upgrade - Lose unencrypted shows?
I want to unhack my tivo ... series 2 with version 4.x something or other software on it to allow it to upgrade. Can I do this and still keep all of my old shows on the tivo and still watch them once it upgrades? Also could use any tips to unhack my drive. I used Sleepers ISO to hack it. I assume if I just remove the upgradesoftware=false or whatever that is wherever it is that it will go ahead and upgrade the new software.
PlainBill
02-18-2005, 10:58 AM
No, you won't be able to watch your old shows once it upgrades. Is this a SA TiVo or a DirecTiVo? If it is a DirecTiVo, it almost certainly has already downloaded (but not installed) the latest update. I am less certain on what will have happened with a SA TiVo.
In any case, the first step is to remove the dual partition set Monte installed by TiVoScripts (Sleeper's). Instructions are here. (http://dealdatabase.com/forum/showpost.php?p=196162&postcount=3)
The next step is to determine if an upgrade is waiting to be installed. The easiest way is telnet to the system and type echo mls /SwSystem | tivosh If it is, search for any of the discussions on 'upgrading in place', and install minimal hacks. It is quite easy to remain at current software levels.
PlainBill
psxboy
02-18-2005, 11:33 AM
Is this a SA TiVo or a DirecTiVo? If it is a DirecTiVo, it almost certainly has already downloaded (but not installed) the latest update. I am less certain on what will have happened with a SA TiVo.
A subbed SA that is making it's daily calls will download a new SW version (when Tivo deems it time for your particular unit to upgrade) and store it in MFS, just like the DirecTivos. At that point it will start rebooting at 2am every night (unless you patch things to prevent that) but the upgradesoftware=false setting will prevent installSw.itcl from ever running.
To the OP, make sure you follow PlainBill's directions for un-sleepering your drive! If you simply un-set upgradesoftware (or set it to true), the software installation process will drop the new kernel & root in the wrong partitions which will prevent your Tivo from booting. Of course, this can be easily fixed if you know what you are doing, and it can be avoided completely by simply flipping the bootpage manually before running installSw.itcl.
-psxboy
A subbed SA that is making it's daily calls will download a new SW version (when Tivo deems it time for your particular unit to upgrade) and store it in MFS, just like the DirecTivos. At that point it will start rebooting at 2am every night (unless you patch things to prevent that) but the upgradesoftware=false setting will prevent installSw.itcl from ever running.
To the OP, make sure you follow PlainBill's directions for un-sleepering your drive! If you simply un-set upgradesoftware (or set it to true), the software installation process will drop the new kernel & root in the wrong partitions which will prevent your Tivo from booting. Of course, this can be easily fixed if you know what you are doing, and it can be avoided completely by simply flipping the bootpage manually before running installSw.itcl.
-psxboy
Seems like a big hassle if I am going to lose my shows. I might as well make a backup of my original drive and restore it for test to my tivo drive just to make sure it works... if it works put my original drive in and let it upgrade so I can then restore it to my 2x160gb drives so I can get the full storage of the lba48 kernal. Seems reasonable right?
eastwind
02-18-2005, 05:24 PM
Seems like a big hassle if I am going to lose my shows. I might as well make a backup of my original drive and restore it for test to my tivo drive just to make sure it works... if it works put my original drive in and let it upgrade so I can then restore it to my 2x160gb drives so I can get the full storage of the lba48 kernal. Seems reasonable right?
Who said anything about losing your shows? If they're not scrambled you will probably be able to play them once upgraded (don't know why not). If they're scrambled, there is a way to uncramble them "in place" or for extraction. Only problem I can think of is if Sleeper's method for not scrambling is uncompatible with the new method.
ew
Who said anything about losing your shows? If they're not scrambled you will probably be able to play them once upgraded (don't know why not). If they're scrambled, there is a way to uncramble them "in place" or for extraction. Only problem I can think of is if Sleeper's method for not scrambling is uncompatible with the new method.
ew
I believe that PlainBill made the point that I wouldnt be able to watch them. They are currently unscrambled. I don't know, which is why I came here to ask :D.
No, you won't be able to watch your old shows once it upgrades. Is this a SA TiVo or a DirecTiVo? If it is a DirecTiVo, it almost certainly has already downloaded (but not installed) the latest update. I am less certain on what will have happened with a SA TiVo.
eastwind
02-18-2005, 06:58 PM
Must be incompatibility with the kmem hack. Can you extract them now? I haven't researched the kmem hack, so I don't know how it works (never used it). If the recordings are unencrypted, you should be able to play them once you re-hack your TiVo (I'm assuming you would do that after the software upgrade). Might need to wipe out the CSO keys or something like that.
ew
PlainBill
02-18-2005, 07:00 PM
I believe that PlainBill made the point that I wouldnt be able to watch them. They are currently unscrambled. I don't know, which is why I came here to ask :D.
I'm sorry, upon reading it, I wasn't very clear in my original post. Let's see if I can do better this time.
You can allow the TiVo to update to the latest software; however IIRC, you will not be able to watch your current recordings until you rehack.
To allow the TiVo to upgrade safely, you must either flip the bootpage and boot parameters or convert to killhdinitrd.
In my opinion, the best course of action is to collect the appropriate killhdinitrd kernel, AlphaWolf's NoCSO patch and his AIO binaries, Jamie's backported USB drivers, and create an rc.sysinit.author file. Once these are collected, convert from a 'two partition monte' to a killhdinitrd system. It is very likely the upgrade software is already on your system. It takes about 30 minutes to do the upgrade, copy files over to the new partition set, update boot parameters and reboot (35 if you use an LBA-48 kernel. At that point you should be running the latest software for your system and ALL OF YOUR RECORDINGS WILL BE VIEWABLE. If future upgrades come down, it will take only minutes to upgrade to them once the patch points are known.
PlainBill
AlphaWolf
02-19-2005, 02:49 AM
I have never used sleepers ISO myself, but I am under the assumption that it uses the older era noscramble kernel patching. In the end, that has the same effect as the newer era nocso method in that the streams are stored plaintext on the hard disk.
However, there is one key difference between the two methods that make and break stream playability dependent on how the tivo is hacked: the (obfuscatorily named) Commercial Skip Offset attribute itself. NoCSO does exactly what its name says; it forces tivoapp to never set a CSO key to begin with, which effectively makes the streams record in plaintext as opposed to being encrypted. The kernel based "noscramble" methods just disable the encryption subsystem in the IDE driver.
The noscramble method leaves the CSO key intact though, so if for any reason the kernel patch is removed, tivoapp will attempt to decrypt a tystream that was never encrypted to begin with which effectively makes it unable to play, hence your problem at hand. This is easy to fix though, you simply need to remove the CSO keys for non encrypted streams. I posted a script a while back which does this automatically, as well as rightfully leaving the CSO keys intact for shows that are encrypted so that they can still play back as well. If you do this, your unencrypted shows will play back fine no matter what state your tivo is in, be it hacked or not.
If I go with the whole update and rehack method I am guessing is there would be no way for me to actually take advantage of the extra disk space that I currently cannot use. I have two 160GB drives and obviously am only able to use about 130 or whatever the cap is. My best bet is to probably get all of my shows off the tivo then install the original 40 gb drive let it update then re-mfstools my two 160GB drives.
My only problem with pulling the shows off my tivo is that I can convert them to mpg with tytools but when it comes to encoding them to divx so that I can reduce the filesize my audio always goes out of sync. Anyone else experience this problem? I am pulling the streams off with tytools and encoding to divx with drdivx. I know this probably isnt the best place to ask this, in the same thread, but thought I would toss it out anyways.
Thanks for all the input.
AlphaWolf
02-21-2005, 03:23 AM
If I go with the whole update and rehack method I am guessing is there would be no way for me to actually take advantage of the extra disk space that I currently cannot use. I have two 160GB drives and obviously am only able to use about 130 or whatever the cap is. My best bet is to probably get all of my shows off the tivo then install the original 40 gb drive let it update then re-mfstools my two 160GB drives.
If you use an lba48 kernel, the limit is in the terrabyte range. Setup an inline monte with one of the kernels posted in the 4.x on RID thread as those kernels have a bunch of other tweaks included as well. I myself use a 160 gig hard disk just fine.
My only problem with pulling the shows off my tivo is that I can convert them to mpg with tytools but when it comes to encoding them to divx so that I can reduce the filesize my audio always goes out of sync. Anyone else experience this problem? I am pulling the streams off with tytools and encoding to divx with drdivx. I know this probably isnt the best place to ask this, in the same thread, but thought I would toss it out anyways.
Theres no real need to pull the shows, see the last paragraph in my previous post. If you really want to go that route though, I would recommend converting the streams to mpeg using an s2 compatible version of typrocess (part of the tystudio package, but don't use tyeditor) instead of tytool, and then use videoredo to make your edits. Typrocess does a better job of error handling than tytool (thus you'll get less dropped video during the conversion,) and videoredo is very good at losslessly post processing the streams so that they will sync with just about anything. After that you can use whatever program you want to convert them to divx.
If you use an lba48 kernel, the limit is in the terrabyte range. Setup an inline monte with one of the kernels posted in the 4.x on RID thread as those kernels have a bunch of other tweaks included as well. I myself use a 160 gig hard disk just fine.
What I mean to ask is, how would I tell it to extend to the full 160GB of my drive when now it is setup to only see 137GB? Aren't there special steps you have to do when you install the drive to make it so that the TiVo can see space. Where as in my case the drives area already in use and have data on them. Are you saying that it would automatically see the extra disk?
Thanks again for the help.
Well I hosed my TiVo.
I did the following... I thought I must have done something wrong .... but it appears I did exactly as this post suggested (http://dealdatabase.com/forum/showpost.php?p=196162&postcount=3) .... I got killhdinitrdutility and a virgin kernel. Uploaded the virgin kernel to the TiVo. Found the bootpage. Copied the new kernel. Changed the bootpage, flip the bootkernel, and rebooted. It sticks at Almost there... just a few minutes more....
I am hoping I didn't lose the shows. If I could even pull the shows off the disk directly and somehow copy them to a windows share on the network that would work for me. Possibly if one of these Linux cds that you have can connect to the network and mount a network share that would be sweet. I dunno. Something like that is what I am hoping. I would just copy it drive to drive but the only drive i have 98 on is a 3 gig drive so it would not have the room to hold the shows.
Anyone have a suggestion as to what I can do?
Thanks
NOTE: The 4.0 (non-enhanced) image does not have the killhdinitrd kernels. If you do not wish to pay $5.00 for the enhanced version, you can download the killhdinitrd utility here: http://www.dealdatabase.com/forum/showthread.php?t=36692 'virgin' kernels from the link in the files section: http://dealdatabase.com/forum/showthread.php?t=38573, and follow instructions in the killhdinitrd support thread: http://dealdatabase.com/forum/showthread.php?t=36693&page=1.
Use UltraISO (http://www.ezbsystems.com/enindex.html) to extract the appropriate killhdinitrd kernel* from the ISO.
FTP the gziped kernel (vmlinux.px.gz)*** to the TiVo. I placed it in /var/packages directory. Telnet to that directory.
Extract the kernel with 'gzip -d vmlinux.px.gz' ***
Determine the 'true' partition set with 'bootpage -p /dev/hda'. It will report a long string that begins with 'root=/dev/hda4' or 'root=/dev/hda7'. The 'true' partition set is the opposite one. If it reports hda4, the 'true' kernel partition is /dev/hda6 and the 'true' root is /dev/hda7. If it reports hda7, the 'true' kernel partition is /dev/hda3 and the 'true' root is /dev/hda4. x is the 'true' kernel, y is the 'true' root.
Replace the present kernel 'dd if=vmlinux.px of=/dev/hdax'
Update the boot parameters 'bootpage -P "root=/dev/hday dsscon=true console=2,115200 upgradesoftware=false" /dev/hda'
Flip the boot kernel 'bootpage -f /dev/hda'
Reboot the TiVo.
Attached is the serial output....
PlainBill
03-10-2005, 10:12 AM
Thanks for attaching the serial output. This section shows you did NOT sucessfully killhdinitrd the kernel: Scan /mnt
Scan /mnt/lost+found
Scan /mnt/var
Scan /mnt/var/utils
Scan /mnt/var/utils/messages
Scan /mnt/proc
Scan /mnt/install
Scan /mnt/dist
Scan /mnt/mnt
Scan /mnt/mnt/tmp
Scan /mnt/mnt/cdrom
Scan /mnt/mnt/card1
Scan /mnt/mnt/card2
Scan /mnt/initrd
Scan /mnt/dev
Scan /mnt/bin
Scan /mnt/etc
Scan /mnt/etc/rc.d
Scan /mnt/etc/tivoconfig
Scan /mnt/etc/tpm
Scan /mnt/etc/rcS.d
Scan /mnt/etc/init.d
Scan /mnt/etccombo
Scan /mnt/lib
Scan /mnt/lib/modules
Scan /mnt/opt
Scan /mnt/opt/tivo
Scan /mnt/sbin
Scan /mnt/tvbin
Scan /mnt/tvlib
<snip>
Recovering from this screw-up is possible. Do you have either the original drive, or the backup image TiVoScripts (Sleeper's iso) made? You will have to extract the original software and apply it to the drive.
PlainBill
Thanks for attaching the serial output. This section shows you did NOT sucessfully killhdinitrd the kernel: Scan /mnt
Scan /mnt/lost+found
Scan /mnt/var
Scan /mnt/var/utils
Scan /mnt/var/utils/messages
Scan /mnt/proc
Scan /mnt/install
Scan /mnt/dist
Scan /mnt/mnt
Scan /mnt/mnt/tmp
Scan /mnt/mnt/cdrom
Scan /mnt/mnt/card1
Scan /mnt/mnt/card2
Scan /mnt/initrd
Scan /mnt/dev
Scan /mnt/bin
Scan /mnt/etc
Scan /mnt/etc/rc.d
Scan /mnt/etc/tivoconfig
Scan /mnt/etc/tpm
Scan /mnt/etc/rcS.d
Scan /mnt/etc/init.d
Scan /mnt/etccombo
Scan /mnt/lib
Scan /mnt/lib/modules
Scan /mnt/opt
Scan /mnt/opt/tivo
Scan /mnt/sbin
Scan /mnt/tvbin
Scan /mnt/tvlib
<snip>
Recovering from this screw-up is possible. Do you have either the original drive, or the backup image TiVoScripts (Sleeper's iso) made? You will have to extract the original software and apply it to the drive.
PlainBill
PlainBill
Yes I have the original hard drive...
PlainBill
03-10-2005, 12:23 PM
Yes I have the original hard drive...
The easy fix is to copy the active partition from the original drive to the 'production' drive. Short form procedure:
Hook up original drive, boot from Linux cd.
Mount fat32 partition on /dos.
Determine active partition set using bootpage -p (I'll assume 4)
Copy using dd [dd if=/dev/hdc4 of=/dos/tivoroot bs=1024]
For luck, get the kernel too [dd if=/dev/hdc3 of=/dos/tivoboot bs=1024]
Shut down, remove the original drive, hook up 'production' drive
Mount fat32 partition on /dos
Replace the root partition [dd if=/dos/tivoroot of=/dev/hdc4 bs=1024]
Replace the kernel dd if=/dos/tivoboot of=/dev/hdc3 bs=1024 *
Verify bootpage -p (should be root=/dev/hda4) and bootpage -b (should be 4)
Shut down, hook drive up to TiVo, cross fingers, boot.
PlainBill
The easy fix is to copy the active partition from the original drive to the 'production' drive. Short form procedure:
Hook up original drive, boot from Linux cd.
Mount fat32 partition on /dos.
Determine active partition set using bootpage -p (I'll assume 4)
Copy using dd [dd if=/dev/hdc4 of=/dos/tivoroot bs=1024]
For luck, get the kernel too [dd if=/dev/hdc3 of=/dos/tivoboot bs=1024]
Shut down, remove the original drive, hook up 'production' drive
Mount fat32 partition on /dos
Replace the root partition [dd if=/dos/tivoroot of=/dev/hdc4 bs=1024]
Replace the kernel dd if=/dos/tivoboot of=/dev/hdc3 bs=1024 *
Verify bootpage -p (should be root=/dev/hda4) and bootpage -b (should be 4)
Shut down, hook drive up to TiVo, cross fingers, boot.
PlainBill
I have both the drives in the system. The original drive is hdb and the new drive I need to repair is hda
I assume I can do the following...
dd if=/dev/hdb4 of=/dev/hda4 bs=1024
dd if=/dev/hdb3 of=/dev/hda3 bs=1024
is this correct?
I have both the drives in the system. The original drive is hdb and the new drive I need to repair is hda
I assume I can do the following...
dd if=/dev/hdb4 of=/dev/hda4 bs=1024
dd if=/dev/hdb3 of=/dev/hda3 bs=1024
is this correct?
Well the first one worked. The second one returned...
dd: writing '/dev/hda3' : No space left on device
2049+0 records in
2048+0 records out
I am not sure what to do now...
Well the first one worked. The second one returned...
dd: writing '/dev/hda3' : No space left on device
2049+0 records in
2048+0 records out
I am not sure what to do now...
I just checked something and think I am royally screwed as far as my old shows...
I just did the following:
PTVupgrade /# bootpage -p /dev/hdb
root=/dev/hda7
PTVupgrade /# bootpage -p /dev/hda
root=/dev/hda7 dsscon=true console=2,115200 upgradesoftware=false
Hmmm... I don't konw what to make of this at all....
PlainBill
03-10-2005, 10:01 PM
Well the first one worked. The second one returned...
dd: writing '/dev/hda3' : No space left on device
2049+0 records in
2048+0 records out
I am not sure what to do now...
Not a problem! Sometimes the kernel partition is 2 Megs; sometimes 4. All kernels start at the beginning of the partition and are less than 2 megs.
You're golden!
PlainBill
Not a problem! Sometimes the kernel partition is 2 Megs; sometimes 4. All kernels start at the beginning of the partition and are less than 2 megs.
You're golden!
PlainBill
Even with this?
PTVupgrade /# bootpage -p /dev/hdb
root=/dev/hda7
PTVupgrade /# bootpage -p /dev/hda
root=/dev/hda7 dsscon=true console=2,115200 upgradesoftware=false
Not a problem! Sometimes the kernel partition is 2 Megs; sometimes 4. All kernels start at the beginning of the partition and are less than 2 megs.
You're golden!
PlainBill
So far doesnt look good. It is sitting at the Almost there. Just a few minutes more... screen and I am guessing since I restored it to the original config that there is no serial output at this stage. I can't tell you what it is doing but it has been sitting here for a few minutes... I will let it sit here for more but i dont have high hopes... :( oh well... live and learn...
PlainBill
03-10-2005, 10:26 PM
So far doesnt look good. It is sitting at the Almost there. Just a few minutes more... screen and I am guessing since I restored it to the original config that there is no serial output at this stage. I can't tell you what it is doing but it has been sitting here for a few minutes... I will let it sit here for more but i dont have high hopes... :( oh well... live and learn...
You're going to hate yourself. Bootpage on the original drive clearly shows that the active partition set is 6 & 7; yet you copied 3 & 4 from the original to the new. Now 3 & 4 MIGHT have been populated - but you never changed the boot parameters or the boot partition. Go back and copy the RIGHT partitions this time; then make sure bootpage -p and bootpage -b on the original and new drives point to the same partitions.
PlainBill
You're going to hate yourself. Bootpage on the original drive clearly shows that the active partition set is 6 & 7; yet you copied 3 & 4 from the original to the new. Now 3 & 4 MIGHT have been populated - but you never changed the boot parameters or the boot partition. Go back and copy the RIGHT partitions this time; then make sure bootpage -p and bootpage -b on the original and new drives point to the same partitions.
PlainBill
If I erased my shows there is no reason to continue. Will they be there if I do this? I am half tempted to put my original drive in and let it upgrade and then just re-mfstools the thing.
PlainBill
03-10-2005, 10:42 PM
If I erased my shows there is no reason to continue. Will they be there if I do this? I am half tempted to put my original drive in and let it upgrade and then just re-mfstools the thing.
No, the software partitions (3-4 and 6-7) are independent of the mfs partitions (well, sort of). If you can get good root and kernel partitions on the 'production' drive, it'll pick up your shows. Just make sure you are copying the right partition set.
PlainBill
No, the software partitions (3-4 and 6-7) are independent of the mfs partitions (well, sort of). If you can get good root and kernel partitions on the 'production' drive, it'll pick up your shows. Just make sure you are copying the right partition set.
PlainBill
Well it is all working. I appreciate all the help. I just tried to telnet to the system and I assume that the telnet, kmem hacks are located on the root partition? Will the system now go ahead and upgrade since it seems I have the stock config loaded onto it? Sorry about sounding down earlier when I said if my shows are gone I might as well just go the other route. I was starting to loose heart... All is grand at the moment for me!!!
PlainBill
03-10-2005, 11:15 PM
Glad to hear it's working. Yes, all your hacks in the root partition were swept into the bit bucket when you booted with a disk that had an intact initrd.
PlainBill
ronrico51
03-11-2005, 12:41 AM
Nice job, PlainBill!
Rick
I am trying to get my Series 2 to upgrade now that we restored from the original disk. Anytime it dials in for a service connection it goes into pending restart mode. My nightlight version with 2.5 does not do this. Do all Series 2s do this? What is weird is that I think there must be some hacks left over from when I had it hacked. I can still watch my shows that should have been unencrypted with the kmem hack. I don't know for sure though about it.
PlainBill
03-13-2005, 08:30 PM
I am trying to get my Series 2 to upgrade now that we restored from the original disk. Anytime it dials in for a service connection it goes into pending restart mode. My nightlight version with 2.5 does not do this. Do all Series 2s do this? What is weird is that I think there must be some hacks left over from when I had it hacked. I can still watch my shows that should have been unencrypted with the kmem hack. I don't know for sure though about it.
'Pending restart' usually means it has downloaded a software upgrade and will reboot at 2:00 AM to reinstall it. IF you have 'upgradesoftware=false' in the boot parameters or early in rc.sysinit, it will not install the upgrade.
PlainBill
'Pending restart' usually means it has downloaded a software upgrade and will reboot at 2:00 AM to reinstall it. IF you have 'upgradesoftware=false' in the boot parameters or early in rc.sysinit, it will not install the upgrade.
PlainBill
My original disk was unhacked. So when we copied over everything would it have wiped out rc.sysinit with an original unhacked version? I understand the software update thing. But it sets "Pending restart" after every time I manually tell it to connect to the service. (I am trying to get it to actually update) The software version never changes. So I take it that it is not normal for it to reboot after every service connection. Unless it won't actually affect the software version and has to do this often until it finally gets updated.
PlainBill
03-14-2005, 07:16 AM
My original disk was unhacked. So when we copied over everything would it have wiped out rc.sysinit with an original unhacked version? I understand the software update thing. But it sets "Pending restart" after every time I manually tell it to connect to the service. (I am trying to get it to actually update) The software version never changes. So I take it that it is not normal for it to reboot after every service connection. Unless it won't actually affect the software version and has to do this often until it finally gets updated.
What is the output from 'bootpage -p /dev/hda'?
PlainBill
What is the output from 'bootpage -p /dev/hda'?
PlainBill
No clue... because I can't telnet into the machine.... I guess I would need to put it into the system here and boot from the ptvupgrade cd and then run bootpage -p /dev/hdx where x is the tivo drive, eh?
PlainBill
03-14-2005, 10:39 PM
No clue... because I can't telnet into the machine.... I guess I would need to put it into the system here and boot from the ptvupgrade cd and then run bootpage -p /dev/hdx where x is the tivo drive, eh?
Yup.
PlainBill
Yup.
PlainBill
Been busy haven't had time to do anything with the TiVo and when I wasn't busy, it was :D
What should I look for and expect to see? Once I see what I see what do you recommend I do? That way maybe once I have it pulled I can check the bootpage and then also maybe do something about it continually rebooting.
Much thanks
PlainBill
03-17-2005, 02:18 PM
Been busy haven't had time to do anything with the TiVo and when I wasn't busy, it was :D
What should I look for and expect to see? Once I see what I see what do you recommend I do? That way maybe once I have it pulled I can check the bootpage and then also maybe do something about it continually rebooting.
Much thanks
In my limited experience, the only time we always see "pending restart" is when the TiVO has downloaded an update, but has not yet installed it. The usual culprit is "upgradesoftware=false" in the boot parameters.
When you run bootpage -p /dev/hdc, I would expect you to see something like "root=/dev/hdax dsscon=true console=2,115200 upgradesoftware=false" (x would be either 4 or 7).
If you type in bootpage -P "root=/dev/hdax dsscon=true console=2,115200" -C /dev/hdc , the system will install the upgrade when it reboots. (Don't do this if you don't want the upgrade).
PlainBill
In my limited experience, the only time we always see "pending restart" is when the TiVO has downloaded an update, but has not yet installed it. The usual culprit is "upgradesoftware=false" in the boot parameters.
When you run bootpage -p /dev/hdc, I would expect you to see something like "root=/dev/hdax dsscon=true console=2,115200 upgradesoftware=false" (x would be either 4 or 7).
If you type in bootpage -P "root=/dev/hdax dsscon=true console=2,115200" -C /dev/hdc , the system will install the upgrade when it reboots. (Don't do this if you don't want the upgrade).
PlainBill
Let's speculate for example that I don't want to upgrade but I do want to stop the reboots. Do you have a post somewhere that would explain this process?
http://www.dealdatabase.com/forum/showpost.php?p=211033&postcount=8
I mean each steps of it. Can I download them to my Win98 disk so that when I put it into the system I can mount it, copy them over, and then install the hacks? I assume that un-killhdinitrd the system is pretty easy if I decide I would like to do a major update. But allowing me to get ftp and telnet working on it again will allow me to try to get mfs_ftp to work correctly. I was unsuccessful at getting it to work which was why I wanted to update. Since I did not need all the extra hacking that leaving it hacked provided. But I would rather get mfs_ftp working correctly and stay at my current software version. And I would like to try this with killhdinitrd. At least that is the idea.
Thanks,
Soul
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.