OldSpiceAP

can you get to a command line - i.e. login and type stuff? If you caN, then try typing this: xfreecfg or xf86cfg or xfree86cfg or xf86config or xfreecfg I use xorg so I don't remember what xfree's config tool is as my remembery is broken. if none of those do anything try typing xorgcfg anyhoo it might do something - or at least give a useable error. eventually you may need to hand edit your /etc/X11/xfree86.conf file or whatever its called as mines xorg.conf - to give it a video mode it can use Let us know what happens also try startx - just to see if it does anything.

lol its happened to me before - now I'm haveing weirder problems though

Update: I followed the link to getting sound to work right in gnome that was provided, and followed its instructions. I noticed no difference. One thing I notice now though is that even when there is no sound, in xmms, the sound visualization beats with the music but slow, and the counter goes slow too - it takes about a minute for the counter to show 10 seconds.

going back on the upgrades won't work well as what I did was moving from warty release to hoary release. What I did: changed apt-sources.list to the hoary one sudo apt-get update sudo apt-get install ubuntu-desktop -r sudo apt-get dist-upgrade I doubt going back from hoary to warty would be a smooth thing. Especially going back from xorg to xfree - yikes. Any other idears ya'll?

Perhaps it has something to do with the kernel on the Damn Small Linux floppy. Try an older version if you can find it - then update.

hmmm let me think... I know I did this with an nvidia card - I had to add a twinview option... Perhaps something like this - thanks to google. Section "ServerFlags" Option "Xinerama" "on" EndSection Section "Device" Identifier "Matrox0" Driver "mga" BusID "PCI:1:0:0" #check this with lspci Screen 0 EndSection Section "Device" Identifier "Matrox1" Driver "mga" BusID "PCI:1:0:0" #check this with lspci Screen 1 EndSection

hmmm let me think... I know I did this with an nvidia card - I had to add a twinview option... Perhaps something like this - thanks to google. Section "ServerFlags" Option "Xinerama" "on" EndSection Section "Device" Identifier "Matrox0" Driver "mga" BusID "PCI:1:0:0" #check this with lspci Screen 0 EndSection Section "Device" Identifier "Matrox1" Driver "mga" BusID "PCI:1:0:0" #check this with lspci Screen 1 EndSection

hmmm let me think... I know I did this with an nvidia card - I had to add a twinview option... Perhaps something like this - thanks to google. Section "ServerFlags" Option "Xinerama" "on" EndSection Section "Device" Identifier "Matrox0" Driver "mga" BusID "PCI:1:0:0" #check this with lspci Screen 0 EndSection Section "Device" Identifier "Matrox1" Driver "mga" BusID "PCI:1:0:0" #check this with lspci Screen 1 EndSection

Hmmm after posting this it didn't show up on the most recent threads on the home pages. Issomething wrong with the forums or is it me?

It may be possible to install the windows programs necessary using wine. What program is used to connect? I know windows media player seems to work well with wine.

What filesystem did you use? If you used reiser4 then you need to use the lilo bootloader as grub can't load a reiser4 partion yet.

Hmmm I recall having similar problems at one time can you open a terminal and type ifconfig and see what the output is? You may need to be root to run the command, but I don't think so. you may need to do an ifconfig ppp0 up or something along those lines.

Well, here is what I would do. Using SuSE 9.1 I'd assume you're running KDE Right? Open a konsole for the commandline. type : rpm -r wine if that doesn't work go into yast's add and remove programs thingy and remove wine. Then surf over to www.winehq.org and try a different wine build that you were using. I'd recommend wine version 20040813 (I think thats it it might be 20040814) download the SuSE rpm and install it. Then open a konsole and type wineprefixcreate. It should work now. The problem is that that was a bug in wine for a while, introduced in december, but has largely been fixed. Wine is a fantastic program but it is undergoing massive changes to the code right now, which is good, but can lead to pains for people such as yourself. It might also be worth trying to get a snapshot of cedega's free version. Cedega is a comercial version of wine tailored to running games. Diablo II runs quite well in wine, with my performance actually exceeding windows on the same machine, so it should all work for ya. http://www.frankscorner.org/index.php?p=diablo2 try there. You can use basically the same instructions for the expansion as well.

worked reasonably fast for me too, I used wine to pull it up in linux.

Bahhhhh, I had the power go out, and as a result my alarm didn't go off. Thus, I was late to work. A truck carrying 18 pallets arrived ahead of schedule thus forceing us to keep them outside, and ugg, problem. We didn't have enough space in our warehouse as our outbound pallets hadn't left yet. Then it started raining.....booooo

Sorry about the duplicate untitled post, I'm not sure where my mind was. Hey all, I'm having some annoying problems with my work machine. Specs: NEC Powermate 2000 PIII 600 128 MB Ram 18 GB HD The machine is an all in one machine with a flat panel monitor built into it. The monitor base houses all components. Problem: This machine is slow! Very very very slow! I'm currently running Ubuntu Warty Warthog, but I previously ran SuSE 8.2 and Yoper 2.1 on it with the same issues. It used to have windows 98 on it but I formatted it off. The problem did not occur in windows but all linux distros run extremely slowly. GNOME is unbearably slow. WindowMaker even is slow - 2-4 seconds just to open the Applications menu by right clicking on the desktop. Up to a minute to switch between Firefox and Openoffice, which is extruciating. What could the problem be? I enabled Unix large disk access mode in the bios but it didn't help, neither did enableing and disabling DMA. There is a 800 MB swap partition also... Anyone know why this machine is so slow?

Update! It worked! Thanks so much! I owe martouf a beer for sure! Visit Kansas sometime and feel free to take me up on it!

When printing from OpenOffice 1.3.1 everything seems to work fine except that I cannot print more than one copy at a time. That is to say I Go File ---> Print then change copies to say...4 then press print. One copy comes out. Just one, no matter how many I tell it to print. Now I just hit the print button a whole bunch of times. Any ideas? Printer is an Optera S Series

I did that and it worked! I wonder though, why did I need to do that?

Forgot to add this link for you. It has much good info. http://www.frankscorner.org/index.php?p=diablo2

To start off download the appropriate version of wine for SuSE that you are running. Since you are using SuSE you should just be able to install it by clicking on the file. ITs extension will be RPM. ONce wine is installed its a good idea to open a konsole or terminal and type wineprefixcreate then type wine -version Now insert the Diablo II cdrom. I assume you are using KDE? if so click on the icon for the CD drive to mount it, but then close it (or right click on the icon and click mount). Now open a konsole or terminal and type wine /media/cdrom0/install.exe DO NOT cd into the directory /media/cdrom0 and run the install program as this will prevent you from being able to unmount the cd drive when it comes time to switch CD's. Once it asks for a new cd you will have to unmount the current cd (right click on icon for cd drive and hit unmount). then insert a new cd and mount it. once it is all installed it should run fine. If no icon is created open a console and try typing wine '$HOME/.wine/drive_c/Program Files/Diablo II/Game.exe' this ought to run it. to make sure its installed and running

one can also use the good ole command line rm -r .wine that will take care of it for ya too

Hehe ok, thanks I feel reaaaalllly smart now.

the letter I as in EYE? or the char | obtained by pressing the Shift + \ key?

Origionally posted by iamroot: ------------------------------------------------ I just bought an MSI Neo V motherboard yesterday to replace my spoilt one and fixed it in just now. ------------------------------------------------ Are you certain it was your board that was bad? Here at my work, such problems occur from time to time as my job is basically testing and troubleshooting of massive numbers of computers each day. The most common cause for this problem is the powersupply. The one that occurs second most is the processor itself. Either of those can cause power failures. If it were the powersupply though it probabily would have been preceeded by some awkward random reboots and such. Also to consider. Some machines are completely picky about ram. We don't deal much with DDR here, but at least with SDRAM, PC133 SDRAM doesn't necessarily work in one motherboard even though it works in several others. I'm not entirely sure why, but I suspect it has to do with voltage for the ram itself. Be sure the voltage your motherboard is set to for the ram matches what your ram uses.