Topic: bored at work... free tech support!
started by: damien_s_lucifer
no newbie questions will be answered.
if your system completely and totally freezes from time to time I'll give 5 to 1 odds it's your cheap ass power supply.
Spontaneous restart is *usually* a power supply problem. The first thing I'd try in the shop would be to plug in the 300 Watt Sparkle Power International Power Supply w/noise killer and see if it solved the problem. It's amazing how many weird quirks disappear with a good PS.
I installed slackware 7.1 this past weekend (mandrake got old), and I've been having a couple troubles... first, whenever I su and chown to spydir (my normal user), and chgrp and all that good stuff, I still have to su to edit anything. annoying as hell. I've tried a couple things, including simply logging in as root and chown/chgrp'ing. I don't really think there's a manual for that (although it's probably in one of the parts I'm skipping over in man chown). Any ideas?
------------------
Spydir Web - spydirweb@techie.com
Core Arctic - < http://welcome.to/CoreArctic/ >
quote:
Originally posted by Spydir Web:
I installed slackware 7.1
Slakware kicks ass!!!! That'd the same thing I run... are you, by any chance, from the SF Bay Area? Walnut Creek CDROM, the guys who develop Slakware, is down the street from my house. They claim to have to most trafficked FTP server in the world... I've seen their setup, and it IS pretty pissed off...
what files are you trying to edit? If they are files in /etc, you'll need to be root to edit them. If you chgrp / chown them, they'll simply be reset to user and group root on next restart, because Slakware does "basic permission sanity checks" every time it starts.
from what I've read, though, I'm guessing you're either 1. not changing your ownerships properly, or 2. creating the files in a directory that spydir doesn't have write permissions in (i.e. /root, or just about any directory other than /home/spydir).
Woever created the files in the first place owns them, so if you were working as someone other than spydir when you made them, you'll have to properly chgrp and chown them (you'll need to be root to do this) :
# change the group ownership to "users" (default for new accounts)
chgrp users yourfile
# change owner to spydir
chown spydir yourfile
The other thing you'll have to do is move your files to your home directory, if they're not there already :
mv yourfile /home/spydir/
if worse comes to worse, you could give rwx permissions on that file to the world :
chmod 777 yourfile # BAD AND SCARY, but it works.
all this, of course, is assuming you have your home directory is on a normal mount, and not something funky like nfs or smbfs.
When I made the original switch from mandrake to slack, I backed up everything to cd-rw's and I copied all the stuff from the cd-rw's right to /spydir and /home/spydir. Things such as my ~/tmp dir, which had a lot of stuff I wanted, and other things created by programs that way I didn't have to worry about redoing everything and having to configure a ton of stuff. When i did the copying (back to the harddrives) I did so as root, so that might be the prob you're talking about.
I also used -R so that I didn't have to go through independent directories (would take hours, I keep my drives organized 
).
I'm not getting ready to chmod 777 anything, but no one ever logs into my machine other then me to really worry about...
You're probably right, I screw stuff up like that a lot . Since it's the weekend now I'll have time to tinker and what not, but thanks a lot for the reminder I screw stuff up pretty easy.
------------------
Spydir Web - spydirweb@techie.com
Core Arctic - < http://welcome.to/CoreArctic/ >
- rm -r your whole spydir directory.
- mount your cd-rw
- su to spydir
- cp everything back.
That way, all the files will be owned by spydir, and not root, and you won't even have to worry about chown / chgrp / chmod.
I also do the two-hd thing. /dev/hda1 is the system partition. /dev/hdc1 gets mounted under /u1 (user disk 1 ), and I made a link from /home --> /u1 for software that makes certain (wrong) assumptions about where user files are.
My roommate also has a machine running Slackware. We have them set up with NFS shares so he can log in as himself on my machine and use his home dir on his home machine, and vise versa... took us a LOT of caffeine to figure that one out
chown YOURUSERNAME /home/spydir -R
the -R command will recursively change the ownership of all the files and directories in /home/spydir.
i repartitioned my ide drive (i have scsi as primary master) so it would be 4 gigs fat, 4 gigs linux.
Then I go through the install process of linux mandrake, installing everything on the 4gig linux drive (it set the swap drive, etc. automatically), then when I reboot, instead of it saying
LILO
boot:
it says:
LI
and it just hangs there. I am running win2k, i dunno if this is a prob. (I installed win2k first then linux).
When I tried using the mandrake boot disk, it came up as:
LILO
boot:
so I typed in linux, and it came back with an error of like .. 0x00 or something, then i saw what else lilo had in there, and it only had linux and rescue to boot from. Now windows (and I did configure it).
Well anyway, I was able to get back into win2k and get rid of the partition, but I would like to know what the hell is the prob and try it again.
------------------
"I'm not dumb. I'm smart in my own way."
anywayz, I haven't had the best of changes to test the idea damein said, but I'll be getting to it tonight. Thanx man, I think it'll actually work
------------------
Spydir Web - spydirweb@techie.com
Core Arctic - < http://welcome.to/CoreArctic/ >
------------------
"I'm not dumb. I'm smart in my own way."
.------------------
Spydir Web - spydirweb@techie.com
Core Arctic - < http://welcome.to/CoreArctic/ >
I have a simple home network. Two machines, desktop and laptop.
Desktop: Win98SE, no-name NIC.
Laptop: Used both NT 4 SP6 and Win98, 3COM NICs.
When I send files from the Desktop to the laptop, things are great, normal speeds (2 M ~ 2 sec).
When I send files from the laptop to the desktop, speed sucks big time (2 M ~ 1 min).
So, what's my problem? Hardware or software, and is it fixable with a software hack/patch or is it only fixable with a new NIC?
Any answers would be great, thx!
------------------
--Jynx
We do not make software "releases" -- our software escapes, leaving a bloody trail of desginers and quality assurance people in it's wake...
------------------
What if there were no hypothetical questions?
-edit double post
This message has been edited by kai on January 29, 2001 at 09:54 PM
Next?
barring that, it's almost certainly a bad NIC.
You do make house calls right?
------------------
"The secret of creativity is knowing how to hide your sources." -
quote:
Originally posted by aventari:
Is that free tech support offer still going on?? I need you to install Samba on my Linux server at home.
I just installed samba on my linux box, what do you need help with?
Is it just like setting up a bootp server for example? Install the software, configure a few files and let 'er rip?
quote:
Originally posted by aventari:
I need you to install Samba on my Linux server at home.
You do make house calls right?
er, no... but Samba is pretty easy to configure. Just make sure you know where it's reading its config files from.
DO NOT USE THE SAMPLE CONFIG FILE!!! It contains entirely too many options. Better to use a simple one and work from there... here's my smb.conf.
code:
workgroup = STARGATE # "Workgroup" setting in Win9x
netbios name = TACHYON # "Machine name" setting in Win9x
hosts allow = 127. 10.0.0. # Change 10.0.0. to YOUR network address
wins support = no
domain master = yes # Make this machine the master browser
interfaces = eth0 127.0.0.1 # allow connections from Ethernet card and internal sockets
lm announce = true # tell all machines you're the Local Master
preferred master = yes # keeps 9x machines from becoming master browsers
os level = 65 # keeps NT / 2000 machines from becoming master browsers
encrypt passwords = yes # if you don't put this line in, you'll have to
# hack your Winbox registries[homes] # This section allows people to browse their home directories
guest ok = no
read only = no[public] # A "public" (actually, LAN-only) directory for sharing files
path = /home/public
guest ok = yes
read only = no# end of smb.conf
This script makes my Linux box the "master browser" on my network, which makes the network a *lot* more stable. If you don't do this, any old machine can become MB - and when that machine takes a shit, your network connectivity is SERIOUSLY impaired until a new MB is elected (about 15 minutes.) Some of the MB config lines are probably overkill, but since my Linux box is the only one that's always on I want to be sure it's the MB.
It also ONLY allows connections from my LAN... change the 10.0.0. part to YOUR network address, which is accomplished by simply dropping the last octet of the IP addresses you use. So if your machines are 24.137.229.1, 24.137.229.2, etc. your network address is 24.137.229.
The "homes" section is cool... login to Windows with your Linux username & password. When you go to the Samba machine, your home directory is one of the shares. Slick. Neato.
Hope this helps.
a few days ago I flashed my mobo bios (abit bp6 to bios rev RU) to fix a problem with win2k not liking my usb. That worked, but now somethin really freaky is goin on. I have to power my computer up twice before it boots.
The first time I hit the button, the power activates, I can hear the fans and such; but there's no hard drive clicking, and nothing on my monitor. I have to hold the damn power button in for 6 seconds (I hate that), wait for the fans to die down, then hit it again and it boots up nominally.
quote:
Originally posted by Vigilante:
a few days ago I flashed my mobo bios...I have to hold the damn power button in for 6 seconds (I hate that), wait for the fans to die down, then hit it again and it boots up nominally.
I think your solution to the old problem is the source of the new once. Email ABit with your complaint and see what they say. Or just wait for the next BIOS revision.
I'm very impatient :]
------------------
"The secret of creativity is knowing how to hide your sources." -
quote:
I think your solution to the old problem is the source of the new once. Email ABit with your complaint and see what they say. Or just wait for the next BIOS revision.
Yeah, yeah, I figured that. I've emailed abit before though, and they never bothered to respond. 
). Now my dilhema, when I try and run certain apps, when they try and start I get a error like "The application failed to initialize properly ([some hex]). Press OK to terminate this program."
Now this is really starting to piss me off. I thought it could be my RAM, so I took out one stick, still got the error, put it back in, took out the other, tryed again, same error. I've even replaced my Mobo and proc (with almost identical mobo 'cept new one had multipliers ) and it still does it...
Any help? Pls? Oh and if your wondering if I can give a specific example how THPS2 cracked hehehe.. starting to piss me off, can't play it on my comp (which is better, and is mine), have to play it on my bro's which is running ME. So any ideas short of switching back to ME or 98 (or wine )?
[Edit: forgot to mention that THPS2 cracked is not the only prog that doesn't work, Netscape 6 doesn't (same error) Q3Radiant some times gives me that crap (IN THE MIDDLE OF COMPILES!!!), etc ]
This message has been edited by DeadAnztac on February 09, 2001 at 11:59 PM
quote:
Originally posted by DeadAnztac:
when they try and start I get a error like "The application failed to initialize properly ([some hex]). Press OK to terminate this program."
something in Windows is corrupt.
do you have a virus scanner? If so, update your virus data and scan.
If you don't find anything, try (re)installing SP1.
If *that* doesn't work, try reinstalling Win2K.