Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - royw

Pages: 1 [2]
16
Developers / What is an External Key?
« on: February 16, 2008, 06:18:57 am »
Howdy,

I've been trying to figure out what is meant by "external key" in LMCE's databases (EK_* attributes).  This wiki page looks cut off before getting to the meat:

  http://wiki.linuxmce.org/index.php/Naming_of_Foreign_Keys%2C_Indirect_Keys%2C_External_Keys

Googling around has left me a little confused.  Is it just a table extension where the external key matches the primary key of the original table with a 1:1 mapping between tables?  Is it a substitution or surrogate key?

Any hints on where to look?

TIA,
Roy

17
Installation issues / Missing .id3 files
« on: February 16, 2008, 05:59:03 am »
Howdy,

When ripping DVDs, sometimes I get the .id3 file, sometimes not.  It appears to be dependent on the target filesystem.  For example, if I rip to core's drive (sda1), then I get .id3 files.  But if I rip to either a second internal drive (sdb1 - /mnt/device/34) or to a NFS drive (/mnt/device/36), then the .id3 is not created.

This is with 0710B3 dvd install core/hybrid.

Anyone else seeing this behavior?

TIA,
Roy

18
Developers / HOWTO local authoritive dns with dhcp updates
« on: February 03, 2008, 11:29:28 pm »
Howdy,

I was wanting an authoritative name server for my local intranet.  I also wanted any dynamic IP's to be visible to the name server.  The name server included with linuxmce is configured as a recursive name server.  Here's the changes I did to configure my core's name server to be authoritative and support dynamic IPs.  Note, the machines on my intranet are private, i.e., not known to the outside world.

I named my intranet "wright.local".  Using a "local" top level domain (TLD) is recommended for private intranets.  Some may prefer to use "lan".  You do not want to use any of the standard TLDs like "com", "net", "org",...

I used the core's default intranet addresses, 192.168.80.0/24 with the core at 192.168.80.1.

I've attempted to verbosely document each config file.  :)

The directions for adapting the config files are included in the named.conf file.

If you want to try this, I would suggest building the config in new directories then swapping with the originals when you are ready (I had a little mess when my core hung and I had to restart with only half the configs ready  :)

So start with creating two directories:
Code: [Select]
  sudo mkdir /etc/bind.new
  sudo mkdir /etc/dhcp3.new

Now copy the contents of the original directories:
Code: [Select]
  sudo cp -arp /etc/bind/* /etc/bind.new
  sudo cp -arp /etc/dhcp3/* /etc/dhcp3.new

Also create a new resolve.conf file:
Code: [Select]
  sudo touch /etc/resolv.conf.new

Then add/change the config files below. 

To create a key for use in rndc.key and dhcpd.conf:
Code: [Select]
  sudo dnssec-keygen -a HMAC-MD5 -b 256 -n user rndc

now get the key from the private file:
Code: [Select]
  sudo cat Krndc.*.private
  Private-key-format: v1.2
  Algorithm: 157 (HMAC_MD5)
  Key: 3+GnSWV5FKxcUu57k7QFxbpvv/xr4fXj2wBVGtdGifI=
  Bits: AAA=

now cut the key which is to the right of "Key: " and paste where needed (replace "<paste your key here>" with the key in the config files).  So an example using the above key would look like:
Code: [Select]
key "linuxmce-dhcp" {
        algorithm hmac-md5;
        secret "<paste your key here>";
};

becomes:
Code: [Select]
key "linuxmce-dhcp" {
        algorithm hmac-md5;
        secret "3+GnSWV5FKxcUu57k7QFxbpvv/xr4fXj2wBVGtdGifI=";
};

Make the logging directory:
Code: [Select]
  sudo mkdir /var/log/named
  sudo chown bind:bind /var/log/named
  sudo chmod 755 /var/log/named

Change all the file permissions per instructions in named.conf. 

Double check everything.   ::)

Then when you are feeling lucky, rename the original directories and then rename the new directories to take there place:
Code: [Select]
  sudo mv /etc/bind /etc/bind.original
  sudo mv /etc/bind.new /etc/bind
  sudo mv /etc/dhcp3 /etc/dhcp3.original
  sudo mv /etc/dhcp3.new /etc/dhcp3
  sudo mv /etc/resolve.conf /etc/resolve.conf.original
  sudo mv /etc/resolve.conf.new /etc/resolve.conf

Finally restart the bind and dhcpd services:
Code: [Select]
  sudo rndc reload
  sudo /etc/init.d/dhcp3-server restart

Check the syslog for any errors:
Code: [Select]
  grep named /var/log/syslog
  grep dhcpd /var/log/syslog

Here's the config files.

/etc/bind/named.conf
Code: [Select]
// This is the primary configuration file for the BIND DNS server named.
//
// This configuration supports an authoritative local zone (wright.local on
// 192.168.80.0/24) and allows DHCP to update the local zone. 
// To customize to your setup:
// 1) replace "wright.local" with your internal domain name.
// 2) edit db.wright.local.zone and db.wright.local.rev and replace
//    my static names/addresses with your network's static names/addresses.
//    Make sure to increment the serial number of any file edited. 
//    Note, format of serial number is:  YYYYMMDDNN where YYYY is year,
//    MM is month, DD is day, NN is update number for that day (i.e., 01,
//    02, 03,...)
// 3) rename db.wright.local.zone to match your domain name.
// 4) rename db.wright.local.rev to match your domain name.
// 5) If you changed the internal network IP from the LinuxMCE default of
//    192.168.80.0/24, then replace "192.168.80" with your network
//    ip and replace it's reverse "80.168.192" wity your network ip's
//    reverse.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
//
// references:
// http://www.arda.homeunix.net/dnssetup.html
// http://www.madboa.com/geek/soho-bind/
//
// notes:
// 1) The following command should be ran about twice a year to keep
//    the root servers current:
//      dig @a.root-servers.net . ns > /etc/bin/db.root
//    Root name servers don’t change very often so updating this file more
//    than twice a year is probably overkill. Frequent updates also put undo
//    load on the root name servers; they have enough to do as it is.
//
// 2) File permissions:
//    /etc/bind/named.conf   root:root   644
//    /etc/bind/rndc.key     root:bind   640
//    /etc/bind/rndc.conf    root:root   600
//    /etc/resolv.conf       root:root   644
//    /etc/bind              root:bind   775, chmod g+s => drwxrwsr-x
//    /etc/dhcp3             root:root   755
//    /etc/dhcp3/dhcpd.conf  root:root   644
//
// Manually Updating Zone Files
// 1. Use rndc to stop BIND.
//      sudo rndc stop
// 2. Remove any .jnl files from the zone file directory.
//      sudo rm /etc/bind/*.jnl
// 3. Edit the zone files as necessary. Make sure to increment the serial
//    number of any file edited.  Note, format of serial number is:
//    YYYYMMDDNN where YYYY is year, MM is month, DD is day, NN is update
//    number for that day (i.e., 01, 02, 03,...)
// 4. Start BIND using its startup script.
//      sudo /etc/init.d/bind9 start


// secret must be the same as in /etc/bind/rndc.conf
include "/etc/bind/rndc.key";

// access control list used to limit queries to local net
acl "internal-net" { 192.168.80/24; 127.0.0.1; };

controls {
    inet 127.0.0.1 allow { any; } keys { "rndc-key"; };
};

include "/etc/bind/named.conf.options";

// The single dot (.) is the root of all DNS namespace, so
// this zone tells named where to start looking for any
// name on the Internet
zone "." IN {
type hint;
file "/etc/bind/db.root";
};

// local intranet zones and reverse zones
// intranet is wright.local and 192.168.80.0/24
// the DHCP servers is on linuxmce-dhcp
// an optional second nameserver would be on linuxmce-ns2

zone "wright.local" IN {
type master;
file "/etc/bind/db.wright.local.zone";
// both allow-update and update-policy can enable DHCP updates,
// but update-policy allows more control over what kinds of
// updates DHCP can perform on a zone.
// allow-update { none; };
update-policy { grant linuxmce-dhcp subdomain wright.local. A TXT; };
// allow-transfer { key "linuxmce-ns2"; };
// notify on zone transfers
notify yes;
};

zone "80.168.192.in-addr.arpa" IN {
type master;
file "/etc/bind/db.wright.local.rev";
// allow-update { none; };
update-policy { grant linuxmce-dhcp subdomain 80.168.192.in-addr.arpa. PTR TXT; };
// allow-transfer { key "linuxmce-ns2"; };
notify yes;
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912 (http://www.ietf.org/rfc/rfc1912.txt)

// Where the localhost hostname is defined
zone "localhost" IN {
// a master type means that this server needn't look
// anywhere else for information; the localhost buck
// stops here.
type master;
file "/etc/bind/db.local";
// don't allow dynamic DNS clients to update info
// about the localhost zone
allow-update { none; };
};

// Where the 127.0.0.0 network is defined
zone "127.in-addr.arpa" IN {
type master;
file "/etc/bind/db.127";
allow-update { none; };
};

zone "0.in-addr.arpa" IN {
type master;
file "/etc/bind/db.0";
allow-update { none; };
};

zone "255.in-addr.arpa" IN {
type master;
file "/etc/bind/db.255";
allow-update { none; };
};


// Include logging config file
include "/etc/bind/logging.conf";

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
//  Because many of our users are uncomfortable receiving undelegated answers
//  from root or top level domains, other than a few for whom that behaviour
//  has been trusted and expected for quite some length of time, we have now
//  introduced the "root-delegations-only" feature which applies delegation-only
//  logic to all top level domains, and to the root domain.  An exception list
//  should be specified, including "MUSEUM" and "DE", and any other top level
//  domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

include "/etc/bind/named.conf.local";

/etc/bind/named.conf.options
Code: [Select]
options {
// tell named where to find files mentioned below
directory "/var/cache/bind";

// file that contains the process id when bind is running
pid-file "/var/run/bind/run/named.pid";

// enable statistics
statistics-file "/var/named/named.stats";
zone-statistics yes;

dump-file "/var/named/named.dump";

// If there is a firewall between you and nameservers you want
// to talk to, you might need to uncomment the query-source
// directive below.  Previous versions of BIND always asked
// questions using port 53, but BIND 8.1 and later use an unprivileged
// port by default.
// query-source address * port 53;

// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders. 
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.

// The forwarders option tells BIND to not use iterative queries itself
// for information it doesn’t already know about but to forward a
// recursive query to the name servers specified instead.
include "/etc/bind/named.conf.forwarders";

// conform to RFC1035
auth-nxdomain no;

// on a multi-homed host, you might want to tell named
// to listen for queries only on certain interfaces
listen-on-v6 { any; };
listen-on { "internal-net"; };

// to allow only specific hosts to use the DNS server:
allow-query { "internal-net"; };

// sets BIND’s default behaviour to refuse all zone transfers.
// Without setting this option, anyone can transfer any zone.
allow-transfer { none; };

// do not generate notify messages for all zones on a restart.
// override for authorative zones
notify no;
};

/etc/bind/logging.conf
Code: [Select]
logging {

channel default_file {
file "/var/log/named/default.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel general_file {
file "/var/log/named/general.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel database_file {
file "/var/log/named/database.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel security_file {
file "/var/log/named/security.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel config_file {
file "/var/log/named/config.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel resolver_file {
file "/var/log/named/resolver.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel xfer-in_file {
file "/var/log/named/xfer-in.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel xfer-out_file {
file "/var/log/named/xfer-out.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel notify_file {
file "/var/log/named/notify.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel client_file {
file "/var/log/named/client.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel unmatched_file {
file "/var/log/named/unmatched.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel queries_file {
file "/var/log/named/queries.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel network_file {
file "/var/log/named/network.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel update_file {
file "/var/log/named/update.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel dispatch_file {
file "/var/log/named/dispatch.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel dnssec_file {
file "/var/log/named/dnssec.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel lame-servers_file {
file "/var/log/named/lame-servers.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};


category lame-servers {
lame-servers_file;
};
category dnssec {
dnssec_file;
};
category dispatch {
dispatch_file;
};
category update {
update_file;
};
category network {
network_file;
};
category queries {
queries_file;
};
category unmatched {
unmatched_file;
};
category client {
client_file;
};
category notify {
notify_file;
};
category xfer-out {
xfer-out_file;
};
category xfer-in {
xfer-in_file;
};
category resolver {
resolver_file;
};
category config {
config_file;
};
category security {
security_file;
};
category database {
database_file;
};
category general {
general_file;
};
category default {
default_file;
};
};

/etc/bind/rndc.conf
Code: [Select]
options {
default-server  localhost;
default-key     "rndc-key";
default-port 953;
};

server localhost {
key     "rndc-key";
};

key "rndc-key" {
algorithm       hmac-md5;
secret "<paste your key here>";
};

/etc/bind/rndc.key
Code: [Select]
key "rndc-key" {
        algorithm hmac-md5;
        secret "<paste your key here>";
};

key "linuxmce-dhcp" {
        algorithm hmac-md5;
        secret "<paste your key here>";
};

key "linuxmce-ns2" {
        algorithm hmac-md5;
        secret "<paste your key here>";
};

/etc/bind/db.wright.local.zone
Code: [Select]
;
; BIND data file for wright.local
; ref. http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-bind-zone.html
;
$TTL 86400 ; time to live : 86400s = 1 day
; Start Of Authority record, proclaims important authoritative information
; about a namespace to the nameserver.
@               IN SOA  dcerouter.wright.local        roy@wright.org (
                2008013101      ;serial (YYYYMMDDNN where N = 01,02,03,...)
                10800           ;refresh (3 hours)
                7200            ;retry (2 hours)
                36000000        ;expire (10,000 hours = 416 2/3 days)
                86400)          ;default minimum ttl
;
; NameServer record, which announces the authoritative nameservers for a particular zone.
;
                IN NS   dcerouter.wright.local.
;
; Address records specify an IP address to assign to a name
;
dcerouter       IN A            192.168.80.1
dad-kubuntu     IN A            192.168.80.21
royw-gentoo IN A 192.168.80.20
;
; Canonical name records, maps one name to another.
;
linuxmce        IN CNAME        dcerouter

/etc/bind/db.wright.local.rev
Code: [Select]
;
; BIND reverse data file for wright.local
; ref. http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-bind-zone.html
;
$ORIGIN 80.168.192.in-addr.arpa.
$TTL 86400 ; time to live : 86400s = 1 day
; Start Of Authority record, proclaims important authoritative information
; about a namespace to the nameserver.
@               IN SOA  dcerouter.wright.local        roy@wright.org (
                2008013101      ;serial (YYYYMMDDNN where N = 01,02,03,...)
                10800           ;refresh (3 hours)
                7200            ;retry (2 hours)
                36000000        ;expire (10,000 hours = 416 2/3 days)
                86400)          ;default minimum ttl
;
; NameServer record, which announces the authoritative nameservers for a particular zone.
;
                IN NS   dcerouter.wright.local.
;
; PTR — PoinTeR record, designed to point to another part of the namespace.
;
1               IN PTR  dcerouter.wright.local.
21              IN PTR  dad-kubuntu.wright.local.
20 IN PTR royw-gentoo.wright.local.

/etc/dhcp3/dhcpd.conf
Code: [Select]
option domain-name-servers 192.168.80.1;
authoritative;

option routers 192.168.80.1;
option subnet-mask 255.255.255.0;

# lease IPs for 1 day, maximum 1 week
default-lease-time 86400;
max-lease-time 604800;

# dynamic DNS updates
ddns-updates on;
ddns-update-style interim;
ddns-domainname "wright.local.";
ddns-rev-domainname "in-addr.arpa.";
ddns-ttl 14400;

# don't let clients modify their own A records
ignore client-updates;

key "linuxmce-dhcp" {
algorithm       hmac-md5;
secret "<paste your key here>";
};

zone wright.local {
primary 192.168.80.1;
key "linuxmce-dhcp";
}

zone 80.168.192.in-addr.arpa {
primary 192.168.80.1;
key "linuxmce-dhcp";
}


option space pxelinux;
option pxelinux.magic code 208 = string;
option pxelinux.configfile code 209 = text;
option pxelinux.pathprefix code 210 = text;
option pxelinux.reboottime code 211 = unsigned integer 32;

subnet 192.168.80.0 netmask 255.255.255.0 {
next-server 192.168.80.1;
filename "/tftpboot/pxelinux.0";
option pxelinux.reboottime = 30;

option domain-name "wright.local";
option domain-name-servers 192.168.80.1;
option routers 192.168.80.1;

default-lease-time 86400;
max-lease-time 604800;
pool {
allow unknown-clients;
range 192.168.80.129 192.168.80.254;
}
}

# PXE booting machines
group {
next-server 192.168.80.1;
filename "/tftpboot/pxelinux.0";
option pxelinux.reboottime = 30;

}

# regular machines
group {
}

# CORE (1) has bad mac address:


/etc/resolv.conf
Code: [Select]
domain wright.local
nameserver localhost

I'm not sure where to go from here.  Is there enough desire to make this a feature in LinuxMCE?  If so, how?

Have fun,
Roy

19
Installation issues / 0710B3 media file sync not seeing nfs share
« on: January 31, 2008, 02:27:57 am »
Howdy,

I finally added a second drive to my core then replaced 0710B2 with 0710B3 amd64.  The new installation went smooth (the plutohome.com/new_installation.php scripts did timeout).  I was nicely prompted on which hard drive to install on.  During install the second drive was discovered and mounted as an internal drive.  Everything I had working previously checked out.

So on to adding a new feature, mounting an nfs share.  Interestingly the autodiscovery would find cifs shares but did not discover the nfs share.  So simply added the share from pluto admin, Advanced, Configuration, Devices.

The share does show up under /mnt/device/36 and I can rip dvd to it and I can play the video from it.  Interestingly, when choosing the file to play, the UI1 screen with the Play, Close, Delete button has the file location as: "File: Disk #2".

When I go to pluto admin, Files & Media, Media Files Sync, I can not find the nfs share.  I can find the second hard disk under /home/public/data/videos/Internal HDD-CORE(sdb1)[35].  That's where I would expect a symlink to /mnt/device/36.

Any hints on what is responsible for creating the symlink? 

TIA,
Roy

20
Developers / What's the difference between EK_MediaType 3 & 5?
« on: January 25, 2008, 08:24:01 am »
Howdy,

When a dvd is ripped, by default FK_FileFormat and FK_MediaSubType are not set.  It's kind of a pain to manually use pluto_admin to set them, so am working on a script to automate it.  While doing so I've noticed that the EK_MediaType is sometimes 3 and sometimes 5 (LinuxMCE DVD or LinuxMCE video file).  This got me to wondering what it should be, LinuxMCE DVD because it's a .dvd file or is LinuxMCE DVD suppose to mean a dvd disc in a player?  I searched the wiki and the forums and didn't find any enlightenment.


$ mysql
mysql> use pluto_media;
mysql> select Path,Filename,EK_MediaType from File where IsDirectory = '0' and Path like '/home/public/data/videos%' and FK_FileFormat is null;
+------------------------------------------+-------------------------------------------------+--------------+
| Path                                     | Filename                                        | EK_MediaType |
+------------------------------------------+-------------------------------------------------+--------------+
| /home/public/data/videos/Action          | The Art of War.dvd                              |            3 |
| /home/public/data/videos/Action          | Last Man Standing.dvd                           |            3 |
| /home/public/data/videos/Action          | Fair Game.dvd                                   |            3 |
| /home/public/data/videos/Comedy          | Operation Petticoat.dvd                         |            5 |
| /home/public/data/videos/Comedy          | Scooby-Doo 2  Monsters Unleashed  WS .dvd       |            5 |
| /home/public/data/videos/Comedy          | Support Your Local Sheriff.dvd                  |            3 |


FYI, these were all rip'ed with 0710B2. 

Thank you,
Roy

21
Installation issues / 704 RC1 comments
« on: July 31, 2007, 12:13:15 am »
Howdy,

I installed 704 RC1 last night and have a few comments.

First, well done!  Much better than 1.1 B2.

OK, my learning curve was on 1.1 B2, where I had a partially functional system.  Part of the learning curve was finding the right hardware, i.e. nvidia 6/7 series video and 2 ethernet ports.  I've just ordered two usbuirt so can not comment on controlling external devices yet.
Display is SVGA TV.  No secondary monitor this time.

I followed the instructions for 1.1 B2 using iso files instead of CDROMs.

Fresh install of kubuntu, no issues except display with nv drivers has bad flickers.

I'd really appreciate if the iso names and the prompts in the installer would match.  I.e., where the installer requests disk 1 & 2, that the naming match the iso names (packages, cache), or even a partial match, ex: linuxmce-1.1-packages-disk1.iso, linuxmce-1.1-cache-disk2.iso.

LinuxMCE installer detected nvidia 7600 GS video and prompted for installing nvidia proprietary drivers.  Said yes, installed, rebooted, reran installer.  Smooth process.  Thank you!  I will forgo commenting on how many hows that took the last time with B2.

The video tests worked like a champ.  Selected UI2.

Decided to try having the system as an MD instead of Desktop.  Seems to have worked this time.  Whoop!

The config wizard has some issues.

I had left the system installing overnight and this morning it was on the video and sound, press next when you can hear and see me.  I let it cycle a few times but never heard audio.  Some feedback on what it is trying or even just a trying combination i of N would be nice.  I got bored and told it to go on to next, figured I'd work the audio issue later.

The main config with the user, room, a/v devices... Is actually pretty good if you are already familiar with the web interface.  Directions for a noob seems lacking.  Also the steps in the left hand column might ought to be disabled as push buttons.  I noticed that if you fill in an entry, then click on the next step in the left hand column, you lose what you just entered.  The wizard is expecting you to click the next button.  Also I was unable to add a new device, in this case an Onkyo DV-SP501.  I could type in the name, but there was no "accept" type button.

Overall the best install experience yet.  Now on to seeing how much of the system I can get working...




22
Users / Video/DVD Issues
« on: July 11, 2007, 07:54:16 am »
Howdy,

I'm just started actually using linuxMCE 1.1B2 a couple days ago (Whoop!) and have a few issues.

The first is in video playback.  Is there an easy way to pause when using the Gyration mouse?  The two ways I've found is to navigate to the "Menu".  To resume, then select the episode or play.  The second method that I found is to small left button click to the track/position arrows, choose right arrow, then don't move the mouse (being careful if you sit it down as the optical can move it).  To resume is simple main left button click.

Ideally I'd like to a "pause/play" toggle button on the playback menu (left most).

The second issue is with DVD ripping.  The first disk to rip always finds the disk info.  But later rips (usually between 2 and 5) will not find the info leaving an "unknown" title.  Once in this "mode" it will never find the disk info until the MD is restarted.  To be fair, this might be because I've been having ISP network issues which might be failing the info fetch.

Maybe a "fetch info" button would be helpful on the rip page.

The third issue is again with DVD ripping.  The title "editor" only allows accepting as is or replacing the entire title.  This is a pain when ripping a series where each disk finds the same title so need to manually replace the title with one that includes the disk number.

Ideally being able to edit and maybe having the option to specify disk number (via a spin control) that would be appended to the title would help.

This kind of segues into the forth issue in that there is no way to edit the title of a ripped dvd that I could find.  Renaming the file on disk  causes the cover art to vanish.  Cover art scanning throws and exception (I've seen the patch in the forums, just need to apply it).

Now on to the positive issues.  :-)

UI2 with alpha blending works nicely (ok a few glitches here and there, but acceptable for Beta s/w)

DVD play works nicely.  HDD play works nicely.  Can't tell the difference.

DVD ripping works nicely.

Thank you!

23
Installation issues / Need to set/reset Web Admin user/password
« on: July 01, 2007, 10:58:14 pm »
Howdy,

After much struggle I have finally got 1.1B2 installed in hybrid single NIC
with fglrx drivers.  But I can't log into the web admin page, I've tried every
account permutation I can think of to no avail.  Is there a default user
account?  If not, any idea how I can reset or add an account?

TIA,
Roy

Pages: 1 [2]