Making the switch (windows to linux)

[Shippou-Sensei]

fuck


heh

i got it to work

i'm a stupid mother fucker who doesn't read things prperly

 

[boskysquelch]

What happened when you used the information given in ubuntuguide.org on this topic...?

slight derail...ish...ooo I'll have to read that..one day...I just assumed coz I'd set up the Ubuntu partition as FAT32..the ntfs_ness of my Windows HDs was unuseable during a Ubuntu session...tho I can see the stuff I can't use it in Ubuntu

 

[Shippou-Sensei]

trying to get my sound card working

man i feel like i'm tempting fate doing this shit

 

[Shippou-Sensei]

damn this vertion is slower ... or at least appears to be as the instaltion is going quite slowly

 

[jæd]

damn this vertion is slower ... or at least appears to be as the instaltion is going quite slowly

What you trying to do...?

 

[Shippou-Sensei]

just installed the 32 bit veriant on ubuntu

and the installation appeared to be slower (could just be my imagination)

 

[Jonti]

slight derail...ish...ooo I'll have to read that..one day...I just assumed coz I'd set up the Ubuntu partition as FAT32..the ntfs_ness of my Windows HDs was unuseable during a Ubuntu session...tho I can see the stuff I can't use it in Ubuntu

No need to be confused! It doesn't matter what file system Linux is using -- you can *read* from NTFS with Linux, but you can't write to it, not without installing special software. Google for ntfsmount to find out more.

Incidently, if your windows partition were FAT32 (XP can be installed onto FAT32) you would be able to both read and write to it from your Linux system, no problem.

(Just to be clear, we are talking about a dual-boot system here. One can read and write to NTFS partitions on another machine just by using Samba on the network.)

 

[boskysquelch]

No need to be confused! It doesn't matter what file system Linux is using -- you can *read* from NTFS with Linux, but you can't write to it, not without installing special software. Google for ntfsmount to find out more.

Incidently, if your windows partition were FAT32 (XP can be installed onto FAT32) you would be able to both read and write to it from your Linux system, no problem.

(Just to be clear, we are talking about a dual-boot system here. One can read and write to NTFS partitions on another machine just by using Samba on the network.)

I'm not at the particular PC or Network atm...but that's been gratefully noted for future doings when I return to it.


I'd presumed a rebuild with an all FAT32 set up would remedy all things...and that has to be done anyway...but am in lazy arse mode atm.

 

[Shippou-Sensei]

any tips on getting a soundblaster audugy se to work?

tried following the tips on the site but i don't get anywhere ... just hissing from the speakers when it tries to play audio

and the systed thinks the cards an le or summin

 

[fractionMan]

Have you visited the soundblaster site. You might be able to download the linux drivers from there.

 

[Shippou-Sensei]

ca0 106-dat lf (on chip)

audgy se (according to the bill)


cat /proc/asound/cards

0 [CA0106 ]: CA0106 - CA0106
AudigyLS [Unknown] at 0xa000 irq 17

and all sound is hissy noise


any clues?

 

[Shippou-Sensei]

yep

no linux drivers

ubuntu say use alsa but i'll be fucked if i can get it to work

 

[Jonti]

damn it (Automatix) won't run with the amd64 vertion i'm running

My apologies, I should have checked. I got a bit carried away, I think, because Automatix is very handy, if only as a list for what can most usefully be added to an installation.

If you have the space, why not dedicate a gig or so to 32bit Ubuntu 5.10? Then dualboot between 32 and 64 bit?

(Perhaps include windows - trebleboot? - as well. Having different systems on the same machine can make it easy to identify faults as hardware or software issues.)

Thinking about this got me musing ... you know, going from 32bit to 64bit *shouldn't* be a Big Deal. Operating system architectures like IBM's OS/400 for its iSeries machines have an abstract, idealised "software computer" which runs the programs and deals with the hardware. Think of the JVM and bytecode. The underlying machine architecture may change, but all one has to do is write a new JVM for the new machine, and all the progs will run just fine. I can vouch for this personally, having worked on a 48bit system that was replaced by a 64bit system -- all our applications continued to run OK, in full 64 bit mode (the binary instructions making full use of the processor size).

Unix and Windows don't work that way; they write to the metal, so programs have to be recompiled from source, rather than just recreated from bytecode. "First write your compiler! Now sort the bugs! Next, recompile and test everything!" A straight-forward, if fundamental, change in machine architecture becomes a Herculean task of re-engineering the entire system, and all its application software.

 

[Shippou-Sensei]

might try a treble boot at some point just to see the diffrence but for now ... *sigh* if i can just get all video and audio working i'll be happy

 

[Shippou-Sensei]

*cries*

it work! it works! i have sound!!!

 

[Shippou-Sensei]

but still no proper h264 playback

and reall bad softsub supprt

 

[lobster]

You need to install the h264 codec, its part of ffmpeg, if you get a compiled version it might not be enabled.
I am running slamd64 which is a 64 bit distro and i can run 32 bit apps without a problem, as long as the 32 bit libs are installed.
You would notice some speed diffrence between a 32/64 bit distro especially media and compiling.

There is experimental write support for ntfs, there is no guarantees at the moment it won;t mess up though.

 

[Shippou-Sensei]

i think i'm not quite up to spped enough on the working on linux to do what i want to do

 

[Backatcha Bandit]

I'd presumed a rebuild with an all FAT32 set up would remedy all things...and that has to be done anyway...but am in lazy arse mode atm. :o[/QUOTE]Use Partition Magic under Windows to convert the NTFS to FAT32, innit!

(Yep, it's on there).