illogic-al

Was that that caldera desktop? If so they're SCO now (SCO-Unix i think)

***UPADTE***

Yup, they're SCO. A google turned up this http://www.caldera.com/products/workstation/

If it were me, I download all the patches etc. you'll probably need and then install the board. Then I'd run the mandrake installation disk and use the upgrade feature so that the hardware (IRQs blah, nforce2 chip) would be detected. It's not necessary but I found that it made things easier to config. (I did this when I upgraded to my ECS K7S5A).

:!: Another biochem major! I'm not alone in the world :D

I also noticed the IBM SERVICE drives which I am assuming to be XP backup partitions. I remember on the old forums there beings discussions about this causing problems with a linux installation. This was before 9.0 came out so maybe the issues were taken care of.

How did you make you're boot disk? Sounds like it's not loading the ext3 module meaning it was made for an ext2 filesystem. Boot disks from distro to distro don't usually work (or after recompiling the kernel).

• freetype devel

libalsa2-devel

libbmpeg1-devel

libdvdcss2-devel

libdvdread2-devel

libffmpeg0.4.6-devel

libgtk+1.2-devel

libjpeg62-devel

libpng3-devel

libungif4-devel

win32-codecs

libmng1-devel

XFree86-devel

 

Did you install everythingon this list. If you're not gonna RTFM at least RTFT.

warms my heart to know this. I should start a request a tutorial site. ACTUALLY i should put these tutorials on my site. YEAAAAAH.

I haven't gotten this to work with 1.1 (tried. failed.) which is why I stressed using 1.2.

Again, I only tested with moz 1.2 (tex version)

Are you using mozilla 1.2 if so ... 

Maybe there is someway to make it work with 1.1 but you're gonna have to figure that out yourself. btw to see the gui you need to have the skin default installed (in the directory ~/.mplayer/Skin/default) if not it won't show.

mozilla 1.2?

FLAAAAAAAAAAAAAME WAAAAAAAAAARS! Just kidding.

do you have the ecs k7s5a motherboard. just curious, didn't think many people had this motherboard.

Yes, it is. have an ECS mobo? The tutorial actually needs to be updated as I've found another config that works (read works better and requires less manual work) that in the conf file. I'll update it as soon as possible but I have classes to worry about now. Fricking pchem.

Well, if you install the binary rpms used for cooker, I am 90% sure that it will require other cooker rpms to satisfy its dependencies.

This time the other 10% is right. The cooker dependencies won't change your system that much. Yes, I have dabbled in the cooker, and yes (oh dear god yes) it can hose the perfection that is your desktop just when you get things going right.

Not only does ogg sound better at the same bitrate IT EVEN SOUNDS BETTER AT A LOWER BITRATE. A 54 kbps ogg sounds about the same as a 128 bit mp3. a 64 kbps ogg sounds BETTER than a 128 kbps. By the time we get up to a 128 kbps ogg it sounds waaaaaaaaaaaayy better than a 256 mb mp3. Ok that last one was a gross exageration. I actually can't tell the difference, but the file is MUCH smaller and to me sounds like the original wave (as does the mp3 at 256 kbps just bigger size.)

That's because it's configurable. it starts at 329. the base specs can be found here. http://www.idot.com/TheStore/Desktop/770Sp...=770&Cate.id=19

 

Also a question about the topic "Not Crazy about Lindows, but this is COOL!" If you're not crazy about windows then why were you on the website. If you like the distro just say so, it's not wrong just because it's the popular opinion. I personally, hate Lindows on purely philosophical grounds. I've never used and this hate is pretty much unfounded, but hey, that's my opinion and I'm sticking to it. If someone .gave me a copy of lindows I'd use it and maybe even like it (I'm sure there must be some way to set up an unpriveledged user account). i'm just saying that don't say you don't like something just because it's fashionable to say so. Do so because you have valid (in your mind) plausible, bigotted reasons for doing so. Ok, I'm finished ranting now. BTW I hate Microsoft but I love Bill Gates. How can you not admire such a ruthless businessman, shitty, bug and spyware ridden (but easy and enjoyable to use) software or no.

Woo hoo - compiled and installed!

 

Now - is there a way of configuring it?  I ask for two reasons?

 

1) It doesn't seem to find my skin - it's in the right place

Where is "the right place", (where do you have it). The directory Skin btw.

2) It crashes every time  :( when I try to view the test movie - whatever trailer that is - It just crashes.  Is there a way to buffer the movie?

Are you using mozilla 1.2 if so ...

::deep sigh::

... this started happening to me and for whatever inexplicable reason I couldn't fix it. But let's see if we can do any better with your prob. First, let's just get mplayer to find your skin then we tackle video playing.

I don't care whether I get credit or not. You can just copy this one and stick it on there. I shouldn't get full credit anyways because I did find the majority of this on the linux howto page. I just feel mine is easier to follow (and right here so you don't have to go searching if you don't want to.)

If it's a tutorial for something else, sure, I'd mail one to you.

try this

make uninstall

in the directory you compiled mplayer in. As your configure try

./configure --prefix=/usr --enable-gui

after doing

make clean

and then

make distclean

. Just pulling this out of my @$$ so I hope it works.

 

Also plf also has rc3 packages which I used. If you've followed the tutorial then you should have all the sources you need, i.e, plf and contrib. the only modification I did was use the qt6dlls provided on the mplayer page instead of the ones which came with the win32 codec package.

got this too once. Make sure libungif-devel is installed (it was for me but you never know) and then

make distclean

then start over the config process.

********UPDATE****************

Ok, I've tried this over and over again and I don't know why but now the only way I get quicktime to play is if I put the plugin in the root plugin directory, i.e., /usr/local/mozilla/plugins. Don't know why it just is. If it doesn't work when you put it in the home plugin directory put it in the root plugin directory. Again, I only tested with moz 1.2 (tex version)

This one took a good bit of googling, especially to find my motherboard. As it turns out all I needed was the specific wording and the hits just started racking up because most of it is already in the linux HOW-TO section (really should search the docs before googling.)

Anyway without further ado, the tut:

1. First thing you're going to need is a motherboard which supports hardware monitoring. If when you go in the BIOS and check there's a page that allows you to see the temp your CPU is currently running at, chances are there's an lm_sensors config for it.

2. I kinda gave away the second thing you're gonna need which is the lm_sensors package from mandrake. You can search for it using rpmdrake or as root at a console type

urpmi lm_sensors

and Mandrake does its magic. Ok, from here on out this is an ECS K7S5A tutorial but you should be able to follow the general steps to get your mobo working.

3. If you don't have the same mobo as me look through the HOW-TOs if you've installed them for mobo. The package is howto-html, search for it in rpmdrake (urpmi doesn't provides descriptions for the various languages). If you don't find it there start googling. For wording I'd recommend lm_sensors your_mobo linux howto. For those of you with the same motherboard:

4. You'll have to edit your /etc/modules.confalias char-major-89 i2c-dev

options it87 temp_type=0x31[/color] and save.

eg My /etc/modules.conf

probeall usb-interface usb-ohci

alias eth0 sis900

above snd-emu10k1 snd-pcm-oss

alias sound-slot-0 snd-emu10k1[/code]

and my /etc/modules.confalias char-major-89 i2c-dev

options it87 temp_type=0x31

probeall usb-interface usb-ohci

alias eth0 sis900

above snd-emu10k1 snd-pcm-oss

alias sound-slot-0 snd-emu10k1[/code]

5. You now have to create a file /etc/sysconfig/lm_sensorsmodprobe i2c-proc

modprobe it87

modprobe i2c-isa[/color].

6. At a root console type

/etc/init.d/sensors start

wait for the OKYou should see some output on your console, probably a couple of ALARMs. Don't worry about it. We just did that to make sure you see output. If you didn't, something's wrong and you are SOL. Sorry. Make sure you typed stuff in properly.

7. Now for the boring part, there's a file you need to edit, /etc/sensors.conf comes in handy with it's little find function).

8. Then make sure that the uncommented (doesn't begin with #) lines look like this

    set in0_min 1.7 * 0.95

   set in0_max 1.7 * 1.05

   set in1_min 2.4

   set in1_max 2.6

   set in2_min 3.3 * 0.95

   set in2_max 3.3 * 1.05

   set in3_min 5.0 * 0.95

   set in3_max 5.0 * 1.05

   set in4_min 12 * 0.95

   set in4_max 12 * 1.05

   set in5_max -12 * 0.95

   set in5_min -12 * 1.05

   set in6_max -5 * 0.95

   set in6_min -5 * 1.05

   set in7_min 5 * 0.95

   set in7_max 5 * 1.05

   #the chip does not support in8 min/max



   # vid is not monitored by IT8705F

   # and is not supported by driver at this time

   ignore  vid



# If 3.3V reads 2X too high (Soyo Dragon, for example),

# comment out following line.

#    compute in2   2*@ , @/2

#

   compute in3 ((6.8/10)+1)*@ ,  @/((6.8/10)+1)

   compute in4 ((30/10) +1)*@  , @/((30/10) +1)

# For this family of chips the negative voltage equation is different from

# the lm78.  The chip uses two external resistor for scaling but one is

# tied to a positive reference voltage.  See ITE8705/12 datasheet (SIS950

# data sheet is wrong)

# Vs = (1 + Rin/Rf) * Vin - (Rin/Rf) * Vref.

# Vref = 4.096 volts, Vin is voltage measured, Vs is actual voltage.



# The next two are negative voltages (-12 and -5).

# The following formulas must be used. Unfortunately the datasheet

# does not give recommendations for Rin, Rf, but we can back into

# them based on a nominal +2V input to the chip, together with a 4.096V Vref.

# Formula:

#    actual V = (Vmeasured * (1 + Rin/Rf)) - (Vref * (Rin/Rf))

#    For -12V input use Rin/Rf = 6.68

#    For -5V input use Rin/Rf = 3.33

# Then you can convert the forumula to a standard form like:

#    compute in5 (7.67 * @) - 27.36  ,  (@ + 27.36) / 7.67

#    compute in6 (4.33 * @) - 13.64  ,  (@ + 13.64) / 4.33

#

# this much simpler version is reported to work for a

# Eltite Group K7S5A board

#

  compute in5 -(36/10)*@, -@/(36/10)

  compute in6 -(56/10)*@, -@/(56/10)

#

   compute in7 ((6.8/10)+1)*@ ,  @/((6.8/10)+1)



# Temperature

#

# Important - if your temperature readings are completely whacky

# you probably need to change the sensor type. This must be done

# with 'modprobe it87 temp_type=0xXX', you can't fix it in this file.

# See ../doc/chips/it87 for details and valid 'XX' values!!!

#

   label temp3       "Processor"

   set   temp3_over  40

   set   temp3_hyst  20

   label temp2       "MainBoard"

   set   temp2_over  45

   set   temp2_hyst  25

  ignore temp1

   label temp1       "Temp3"

   set   temp1_over  45

   set   temp1_hyst  25



# Fans

   label fan1       "CPU Fan"

   set fan1_div 8

   set fan1_min 3000



   ignore fan3

   set fan3_min 3000



# This worked for my second fan so I'll include it    

   label fan2        "MB Fan"

   set fan2_div      8

   set fan2_min      2500

9. Right then, now the worst is over. At a root console type

/etc/init.d/sensors restart

to enable our little changes and it's time for the promised gkrellm integration. For those of you who may not want to check this graphically, the sensors-12V: -12.24 V (min = -12.60 V, max = -11.38 V) ALARM

-5V: -6.27 V (min = -5.15 V, max = -4.70 V) ALARM[/color] from what I'm been able to tell. I just ignore it.***

10. Now you need Gkrellm if you don't have it already you need to urpmize it:

urpmi gkrellm

I however would recommend that you get gkrellm2 in all its anti-aliased (fonts don't look like my sister scribbled them) glory. To do that you have to add a texstar source to urpme. I explained this here http://www.mandrakeusers.org/viewtopic.php?t=2644 . Then just do

urpmi gkrellm-2

urpmi will, hopefully, take care of the rest. Once that's done ...

11. It's screenie time! Once installed start gkrellm from the menu (if it got added that fast) or type it in at the run dialog (or whatever you gnomes use)

12. Now since you already have the plugins installed, it's a cinch to monitor you CPU et al with just the click of a button. Click on the gkrellm window and then press F1, the configuration dialog should pop up. You can also get there by right clicking on the gkrellm window. Once at the configuration window click on Sensors.

13. Click on the little white triangle beside Temperatures like so

or just edit the Label

Well that all folks. Gonna go (continue thanks to zapping) watching the superbowl. Go RAIDERS!

I've done this before so this should work.

 

1. Use you're backup disk to install XP, let it do whatever.

2. start XP and dont do anything except disabling system restore and defragging.

3. Install PM, don't bother defragging just resize XP.

4. Reboot and let PM do its thing.

5. Install linux.

6. Boot into XP and reenable system restore if you think you'll need it. Chances are you will.

To test things out you can try here http://www.apple.com/trailers/fox/x2/large.html

I just got this to work myself so while it's fresh in my mind i figured I'd put up a how-to right here.

1. Go to http://www.mplayerhq.hu/homepage/dload.html and download MPlayer v0.90rc3 source.

2. Untar the package into some directory, from the command line this would be

tar xvzf MPlayer-0.90rc3.tar.bz2

.

3. Open up a root console, i.e. open a console and login as root.

4. You may need some devel packages before you begin. Here are the ones I remember using

• freetype devel

libalsa2-devel

libbmpeg1-devel

libdvdcss2-devel

libdvdread2-devel

libffmpeg0.4.6-devel

libgtk+1.2-devel

libjpeg62-devel

libpng3-devel

libungif4-devel

win32-codecs

libmng1-devel

XFree86-devel

If you type these into the rpmdrake search box both the package and dependency will be selected. You could also use

urpmi name_of_package

and that would work too.

*** the NEW win32-codecs package from plf includes the quicktime dlls needed. If you already have the old one you'll need to get the new one for this to work. Or you could go to the mplayer page and follow their instructions.***

5. Before I forget you'll need to add some contrib and plf sources to urpmi. There is an easy to use interface for this at http://plf.zarb.org/~nanardon/ you can select plf, contrib and I'd also suggest texstar sources from this location. eg

(Don't actually use this example because it may not still work.)

6. Now that you have all the mirrors and packages you need, the build can actually start. You can type

./configure --help

to see all the possible options and enable or disable whatever you want, orrrrrrrrrr you can just use mine which enables the gui to mplayer and some other stuff like xv

./configure --prefix=/usr --enable-gui --enable-gif --enable-png --enable-jpeg --enable-xv

A lot of these options are auto detected but I just like to make sure :)

7. Hit enter and wait for configure to finish. Hopefully you won't have any errors. If you do make sure you installed all the recommended devel packages. This configuration should allow you to play divx and microsoft avi files, mpeg files and quicktime files. Of course we're not quite there yet. Any config errors usually hints at what is missing. -lbzip for example refers to libbzip (or zlib) devel packages (i forget which). If you're told of a specifc file like libavcodec.so missing you can search for it in the rpmdrake search box.

8. After getting through config with hopefully no errors it's time to start make. Type

make && make install

This should build and then install mplayer all in one shot. Remember you should be logged in as root at the console. If not you'll get errors during the make process.

9. Now we have to get you a skin for mplayer or the gui wont show up. Go back here http://www.mplayerhq.hu/homepage/dload.html and pick out any skins that you like. Then at a console (yes again)

mkdir ~/.mplayer

mkdir ~/.mplayer/Skin

Then untar you skin to that directory

tar xvjf my_leet_skin

NOW GET READY (unless I forgot something or you're just SOL) and at the console type

gmplayer

and BEHOLD you're new video player.

10. When you start it up it's going to be whining about somefont.ttf. I just copied an arial truetype font to the ~/mplayer/font and select a font. Since they were on the mplayer download page I used those in the mp-iso-8859-7.tar.bz2 package. I assume you know how to untar now so I'll leave you to it.

11. Once that annoying font problem is taking care you'll hopefully have a fully functional mplayer and can make an entry in the menu or on the desktop for it. Now for the final leg.

12. To be able to play quicktime videos from webpages like quicktime.com. you'll need the plugin. For that go to http://mplayerplug-in.sourceforge.net/ and download the mplayerplug-in v0.33 plugin version. Untar it somewhere and then enter the directory.

13. You'll have to open up a console and log in as root (if you're not root already) and then type

make

That's it. Then all you have to do is copy the plugin to you're mozilla/phoenix/netscape/whatever_other_gecko_browser_you_use plugin directory (which is ~/mozilla/plugins for mozilla).

I tested it and the plugin doesn't work with konqueror (yet) and I haven't tried phoenix et-al. Happy vid playing. Gratz.

Well I just built two comps using ecs (mine) and asus (grandmom's) mobo. Stay away from ECS. If you want a low end vid card I'd go with: nvidia nforce2 mobo (asus has em)

high end vid card geforce 4

512 mb of ddr ram

case with 400W power supply

Fastest athlon you can get

and any monitor you like

Personally i'd go for a 16x DVD-rom and 52X burner

soundblaster audigy, the linux drivers shold have most features implemented buy now and you can get all this at fabulously low prices at http://www.newegg.com