somedude

If I knew what that means... :) Just kidding, I will do some reading, I've never used ssh. Your post leads me to believe that there are ssh tools in windoze. Thanks for the advice. Update: oops, looks like my SCO server doesn't have ssh. I can get open ssh for both, but I was hoping there's an easier way.

Hi everybody, I have a UNIX server connected to one of the two UPS units. The other UPS is running two windoze servers. There is a USB connection from both UPS's to the domain controller (sorry - windoze), which sees them as a battery. I set the events to shutdown the server when the battery level drops below a set level. The other windoze machine works very well with this setup. So far so good. I would really like to shutdown the UNIX server when a power failure lasts too long. Since the windoze server monitors the event, I could use a script to shut down the UNIX server remotely, except I don't know of a way to do it without being specifically logged on. There is no USB on the UNIX machine and I don't think SCO would be able to see it either. I tried the remote shell (rsh), for which windoze has a command, but I can't get it to work, because I can't specify the password. Telnet needs an interactive password, so I can't use it. I tried adding the windoze server to /etc/hosts to no avail. Since it's on a secure LAN, I don't mind sending the password across, if need be. I know this is not Linux, but I would really appreciate a clue. Thank you very much. [moved from Networking by spinynorman]

Instead of hitting enter, hit F1 and type expert at the prompt, then follow the instructions. It may work.

Although I've no clue what xgterms are, if you can launch it when logged on as root but not as a regular user, you may not have rights to it. Or, when you're logged on as root, a configuration file may be different than the user's, since it may be in /root instead of /home/user. Sorry if I'm way off here. Try this for Grub.

You know, a great man once said: "One can make mistakes, but you better not make the same one twice or your a$$ is FIRED!" ;)

What you're describing is called a virtual screen. Your resolution is set to more than what the monitor is set to. Does anything change when you hit Ctrl Alt and the + or - keys on the numeric pad?

Do you click on 'Delete' or on 'Send to Trash'? I assume you are using the context menu (right click on a file). If you hit the delete key, it goes to trash, unless you hold shift.

Not sure if this is the case, but you should be cautious when using Netscape. Your best bet is to right-click the link and say 'Save Link Target as"

"Don't support Linux"... Why do they provide drivers, then? Just to screw us up? This is actually what I was going to do next. Load Mandrake on hda and leave the other stuff on the PATA drives connected to the TX2. This way I may be able to load the driver so that Linux can use them too. I will then wait for the 2.6 kernel to support the Promise junk. Jeff Garzik, one of the kernel developers, is looking at it. Oh, well... Thanks guys for your support.

Latest news (still bad, though): I installed 10.0 with the 2.4.25-2mdk kernel and compiled the driver. I thought it didn't compile at all, it was a matter of seconds. So I got my pdc-ultra.o module, put it on a ext2 floppy and tried to install Mandrake (for the n'th time). Here is what I had to do to load the module: - hit F2 at the installer startup menu (F1 works too) - forced 2.4 kernel with 'alt1' (I have no idea how to force expert with the alt1 kernel - any ideas?) - went through the few steps to select a CDROM installation and got to the language selection screen - did an Alt-F2 to get to the prompt - insmod floppy - mkdir /mnt/floppy - mount -t ext2 /dev/fd0 /mnt/floppy - insmod /mnt/floppy/pdc-ultra.o Module loaded (forced) with warnings, due to the kernel difference (compiled for 2.4.25-2mdk but the installer is using 2.4.25-2mdkBOOT). I figured this shouldn't be a problem. Well, this is as far as it went. I got some warnings like: <4> pdc-ultra: [warning] submit cam busy and errors: <4> SCSI disk error: host 2 channel 0 id 4 .... return code 27070000 My drives were detected, size and all, but they weren't, how shall I put this - useable. /proc/scsi is empty The installation process ends with an error: /proc/partitions doesn't agree with drakx 5 != 0 Drakx was willing to nuke my partitions, as it thought the partition table is corrupt. (I told it to bugger off). However, fdisk, after taking a few seconds to examine the disks, did give me the right partitions for both sda and sdb. I am at a loss. The driver seems to have compiled properly and for the first time I get messages about my drives being recognized by Mdk 10 installer. Well, maybe recognized is not right, identified. I would really appreciate some suggestions. Thank you.

Gnomemeeting works under mdk as well. You can also test the cam with xawtv.

It's either available in the expert installation mode or when time comes to setup lilo, there may be an advanced button. I'm sorry I can't remember exactly where. IIRC, that's where you can change the labels, the default and other options. I think it's towards the end of the installation process.

I think you need to comment out the "Display" entries that show a resolution greater than what you want. Don't forget to back up your config-4 file, just in case my advice makes your X blow up. ;)

xp and 2k have a conversion utility that allows for fat32 to ntfs (not vice versa)

Dude, Mandrake IS the most user friendly distro and the easyest to install. I've gone through every version since 6.0 and they were all better than the previous one. I tried the 'flagship' - RedHat and gave up on it quickly. I'm too lazy to move away from Mandrake. (Read that as busy... :) I almost forgot - I installed 10 on three different hardware configurations, including a laptop, successfully. Only one glitch, with the eth0 not coming up at boot, easy enough to correct.

By the looks of it, it's just a 'dumb' deck, the only connections being the in/out to the sound card. There is a serial cable connection that may be used for remote controlling the unit. I'm just guessing, though. Therefore, it may work with Linux. Manual

Hey Guys, I was unable to do anything this weekend, but I'll try again today. I will hook up my drives to the built in controller and load 10.0 with the 2.4 kernel. I will then try to compile the driver from source and do an expert install and load the driver then. I will keep you posted. Just knowing that somebody is reading this thread makes me feel a little more confident. Thank you.

Isn't it also possible to install lilo on hdc and then select which drive to boot to (recent BIOS's let you hit F8 or F12 to select the boot device)?

Do you mean you get a DOS style text prompt? Type startx and hit enter.

I'm having similar trouble with a PDC20375 controller. See this post. Doesn't look like there's much that can be done. I will try to compile drivers for 10.0.

I've had the installer freeze on me while using an USB mouse. Usually, while moving the mouse or clicking. You might want to try with a PS/2 mouse, of course if that is the case.

Update: The Promise boot disk for Mdk 9.0 (the only way I can get my PATA drives recognized) contains the following in syslinux.cfg: label promise kernel vmlinuz append initrd=cdrom.rdz ramdisk_size=32000 root=/dev/ram3 automatic=method:cdrom,insmod:pdc-ultra vga=788 The only difference is the insmod:pdc-ultra command. If I try to insmod the pdc-ultra module in 10.0 (2.6.3) I get a module not found. If I insmod it (alt-F2 console) when I boot the 10.0 CD (2.4 kernel) it does load, but there are problems detecting the hardware. I would really appreciate a few pointers. Right now, I think my only way out of this is to try to install 10.0 with the 2.4 kernel and the promise driver. My plan is as follows: - disconnect the drives from the PDC20375 and connect them to the mobo controller. - load 10.0 with 2.4 kernel. - compile the driver with the 2.4 kernel - pray that I end up with a .o driver that I can copy to an ext2 formatted floppy - create the floppy with the driver - reconnect the drives to the Promise controller - boot the 10.0 cd and pick the 2.4 kernel - do the advanced install and use the driver floppy - pray that it works. Notice I have two steps that start with the word 'pray'. Please let me know if the scenario I have above will (may) work and if the two steps I'm not sure about will (may) work as I think. Thanks again.

If you don't mind me asking, what was it that you couldn't get done in 4 years? And I must add, I'm not being sarcastic, just curious. And the floppy boot setup, were you just cautious, or was there another reason? Because XP can coexist with Linux and Lilo can boot either one.

This could be interpreted a couple of ways. As tyme said, you need to burn the image to a cd. Nero has an option like 'Burn image to disk' or 'Create disk from image' or 'Burn Image'. Do not attempt to create a bootable CD with the .iso file on it. Or a data CD or anything that doesn't say 'image'. Also, Nero's default image format is not iso, so you may have to select .iso or all files to see it so that you can select it before the burn. Oh, that's not multiple extensions, just one: .iso. The i586 just means it's intended for Intel 586 (Pentium) class processors (no 486's). You can have that even in windoze. Just rename a file called mytextfile.txt to mytextfile.txt.crap.dos.txt and it will still work.

It's X window (system), not windows. Sorry, but you might as well learn the 'proper' lingo. When you say you can start X with XFdrake, what do you mean? How far can you get? Do you just get a blue screen and a mouse cursor? If you managed to go though with the configuration and it said all's well, try startx again. And a word of advice, look at the number of penguins people have on their avatar frame. Listen to the ones with many Tux's. B) Check the KDE configuration as posted above.