Cannot edit existing or add new scheduled programs

[tahoejoe]

My scheduled program could not record this morning because I had run out of space on my USB drive.  Took programs off the usb dive to create space. When I tried to reschedule the program, it would not save the program after clicking OK.  I then tried to edit an existing program without any success.  Same was true with trying to delete a program.    Tried soft reboot and also pulling power to reboot.  Also tried a different usb drive.
Any help would be appreciated.

[heyrick]

If you can get a command line (can you telnet in to your OSD?), then:
  cd /media/ext/data
  mv scheduler.sql scheduler.sql.disabled
  reboot

And once the OSD restarts, the scheduled recordings will be cleared so this function will work again.

The previous data file is now called "scheduler.sql.disabled" in case you wish to attempt to copy it to a PC to try to see if anything can be recovered, but to be honest if the file has been damaged somehow, it is often qucker just to set up the data again. You do erase old recordings don't you? Don't let the file get too cluttered, that can't be useful...


If you cannot telnet to your OSD, it is harder to say what to do, for the different versions of the OSD's operating system are all slightly different. Go to the main menu, then to Advanced Applications. On OSDng you will be dropped straight into the command line, but I think on Arizona (Torfu?) you need to then select Terminal.
Either way, you should end up looking at a big square overlay and something that looks like:
  Terminal Ready
  $

Press an arrow key on your remote to pop up the virtual keyboard, then enter the commands carefully. It isn't too pleasant doing it this way, but it is possible! Once you press |Enter| on the virtual keypad, you need to press the Enter key (again) to actually perform the command. And remember, it IS case sensitive, so enter it all in lower case.

Reminder:
  cd /media/ext/data
  mv scheduler.sql scheduler.sql.disabled
  reboot


For geeks - I suggest mv instead of rm so the original file is still available.

[tahoejoe]

Thanks for the response. I've never used telnet to get into my OSD and I'm not sure on how to do it.  I searched the forums and found a thread that said it if the scheduler file was corrupt, it could be cleared by restoring to factory defaults.  So far, that seems to have worked.

[greyback]

Yep, "Restore to Factory Settings" will do the job. It effectively does what heyrick said.

For reference, you get this menu option by pressing the Xim key while at the main menu.
-G

[pfft2001]

Yep, "Restore to Factory Settings" will do the job. It effectively does what heyrick said.

For reference, you get this menu option by pressing the Xim key while at the main menu.
-G

Yes, but Restore to Factory Settings does some other things that you might not like - it's the "big gun" that resets everything.  After doing it, you will have to run the "Initial setup script" again, to setup your network settings, IR config file, and one more thing that I can't think of right now.  Also, you will lose your default recordings setup.

To the OP: you should become comfortable with telnetting into the OSD - assuming your OSD is network connected.  Even if you don't need it this time around.  And, if the OSD is not network connected, you can also get in via the serial port.  (And, if you apply the hack I posted a few days ago, you won't even need to login on the serial port...)

[tahoejoe]

I am network connected.  Is there a tutorial posted some where to set up telnet into the OSD?

[heyrick]

Yep, "Restore to Factory Settings" will do the job. It effectively does what heyrick said.

...with all the tact of Ripley when she said "I say we take off and nuke the entire site from orbit. ... it's the only way to be sure."

[heyrick]

I am network connected.  Is there a tutorial posted some where to set up telnet into the OSD?

How to exactly set up the OSD depends on whether your network uses DHCP to assign network addresses automatically, or if each machine has a fixed address. My network is the latter, so my OSD has the address 192.168.0.12.

To talk to it, I just (on Windows) press the Windows logo key and R at the same time. The "Run" dialogue appears, into which I type:
  telnet 192.168.0.12
and, well, that's it. A windows appears inviting me to log in to the OSD.

But... getting the network stuff set up... take a look at http://www.heyrick.co.uk/blog/index.php?diary=20100508 - though note that this is for the OSDng firmware which is more or less the same as Arizona in this respect.

If you need any more help, that's what these forums are for!

[tahoejoe]

That was easy enough!
Thanks!

[greyback]

Yep, "Restore to Factory Settings" will do the job. It effectively does what heyrick said.

...with all the tact of Ripley when she said "I say we take off and nuke the entire site from orbit. ... it's the only way to be sure."

Nicely put
-G

[pfft2001]

How to exactly set up the OSD depends on whether your network uses DHCP to assign network addresses automatically, or if each machine has a fixed address. My network is the latter, so my OSD has the address 192.168.0.12.

Let me add that even though your router does give out DHCP addresses (I say this because I don't think there are any routers commercially available that don't), you should always configure the OSD to have a fixed IP address.  This is because (AFAICT) the OSD doesn't  broadcast a recognizable "NETBIOS" name - so if you set it up with dynamic IP, you may not be able to find it from the other machines on your LAN.

[heyrick]

give out DHCP addresses (I say this because I don't think there are any routers commercially available that don't)

Unless you switch it off, that is. 

you should always configure the OSD to have a fixed IP address.  This is because (AFAICT) the OSD doesn't  broadcast a recognizable "NETBIOS" name - so if you set it up with dynamic IP, you may not be able to find it from the other machines on your LAN.

VERY good advice, I'll add that to my blog page. [done]