i feel like OP is a bot
i would try booting to some bootable media... linux liveCD is always my first choice in that regard. see if the issues persist with video if nothing else. also google your stop error (all 5 of those hex numbers in the same query)... im on a mobile device so it would be a little annoying for me to do that. but its possible that those numbers together indicate a specific issue.
that first connection shoumd probably be your LAN connection, but you didnt list it as eth0 like one would expect... and it doesnt have an IP address. check your network manager, make sure it's set up appropriately... that is, for dhcp/manual... also dns servers and appropriate subnet mask. you mentioned that it connects to a "windows network"... is this a work computer? if not, is there something about your network that makes it a windows network?
please do a sudo ifconfig -a that will show the status of any connections that are down. possible that eth0 (or the equivalent for your machine) is simply down, and a sudo ifconfig eth0 up (for example) would be a (likely too-easy) fix. a second possibility is that a reboot might resolve it... cold restart if a warm one fails.
i dont want to get too deep while we're still guessing here, so that's it for now.
Perhaps we just dont understand exactly what the sound is. Regardless, the operating system that is on a computer should not cause it to make any abnormal sounds.
You'll want to access your BIOS. The very first text that comes up when you then your computer on tells you how to do that. Also, do a quick Google or Wikipedia search on BIOS si you understand what it is.
reset your modem. they save the MAC address of the device they're connected to, so whenever you change that device, it needs to be reset.
you may have to run a channel auto-programming function, similar to actual TV's. this is a shot in the dark, but that's all i've got. have you verified that the cable is good by hooking a tv up to it?
i actually just ran into a problem similar to this with my brother's laptop. one possible fix is going into the BIOS and changing the hard drive's mode to IDE. Forgive me, i forget exactly which setting it was... something to do with AHCI...
look up "internet connection sharing" for whichever version of windows is on the computer. you'll specifically want to look up wireless connection sharing. it's overally pretty easy.
it could be a hardware problem. how do you feel about looking up online how to open up the case and checking it out in action?
hmm id start by just trying to get to port 80... using something like nmap to see if it can tell it's up. Then try to justuse the default example page xampp includes (they do include one, right?) The error might lie in where you placed the pup files in your file system.
assuming that you conducted an exhaustive search online for the drivers, then it's possible that the network adapter isn't compatible with vista for some reason. was it working with win7?
looking on toshiba's site, it looks like it only shipped with 64-bit windows 7. do you have windows xp available to do a test install, to see if it'll work out of the box on the computer?
i'd look up the beep codes online for your model of computer. the pattern of beeps tells you what the problem is.
additionally, the display should work to some extent. is the monitor connected through VGA or DVI (or HDMI for that matter) ?
what model of computer is this?
how far do you get? are you able to see what you want to access, but are unable to access them? what error message do you get (f any) ?
reaching far back here... but i think the boot record is being pointed to wherever the GRUB was. i'd start by booting with a win98 boot disk to the DOS prompt (i use usb floppy drive), then using fixboot and/or fixmbr.
Interesting. What other programs? There must be something in common...
hey, i actually do tech support for fios. won't charge you for this one.
the driver you installed for your wireless card (usually comes on the CD with the wireless card)... is it for vista? have you restarted the computer?
click start -> right click 'computer', click 'hardware', click 'device manager'... is your wireless card listed under 'network adapters'? if it isn't, that's a problem... if it is, does it have an alarming symbol next to its icon?
we're just getting warmed up here... we just need to gather some info. this will be easy to solve once we get the right info.
oh and i have to ask (i should've asked this first)... do you know how to connect your computer to a wireless network? i can't express to you how many calls i get with fios where this is the exact case... they say all computers but one work, but the only issue is that the installer set up all the other computers, just not the one that 'isn't working'.
or use msinfo32 from the run dialog box. or go to start -> my computer (right click) -> properties ... and that'll show you some abbreviated system info.
i would try checking the page source code to see if that's what's blurring the text. i mean, it most likely is what's causing it... and then you could contact the administrators of the page to see if they're doing that. if it's not... well i don't really know what it could be, but at least then you would have eliminated one possible source of the problem
sounds like the bios is taking a long time to make the PCI video card start running, and then the monitor takes a long time to start running after signal starts being sent to it.
i would start by turning 'quick boot' off in the bios (if it's not already off)... make it run a long boot with a full POST. see if your monitor can catch any part of it before the windows screen shows up.
also, if you try to get into the BIOS while the monitor is plugged into the PCI card, are you able to see the BIOS after a few seconds?
you might try seeing what BIOS version you have... also see if there's any update available for it.
i googled those stop errors and got some fun info. exact search terms were "(address) stop error" and "(address) address". the (address) = 0x7e, 0x50, 0x19 one at a time
i'm not really into using programs to kill viruses, so i'll offer a different perspective.
how do you know it's a virus? maybe the service that the svchost wants to run is necessary for you. svchost, as you should know, is a generic name for the process that shows up in the task manager for any number of running services.
if the svchost isn't slapping you across the face and telling you that it's malware, i would run a "sfc" from either the run dialog or the command prompt. google that to see what exactly i'm talking about.
sounds like your BIOS might only be wanting to boot from the DVD drive... or your hard drive might have failed and it can't boot from naything but the DVD drive.
first think you'd want to do is go into your bios and disable booting from the DVD drive. should be a button you press to get into the BIOS right @ startup... del or f1-f12. the options inside the BIOS are pretty self-explanatory... do a google search if you can't figure that out, there are plenty of pages out there explaining BIOS usage. you'll want to get very familiar with them.
+1 to renan. this is why frequent backups, frequent virus scans, and intelligent web browsing are necessary. don't be too attached to your current OS install... you should always be willing to reformat your HDD and reinstall. destruction and reconstruction are always faster and more satisfying than repair.
i don't know how professional you'd consider me, but my first step in this would be to check and see how long packets take end-to-end. also test out a couple different solutions... it shouldn't be difficult to implement them for a single testbed. that's just my opinion as a single-user solution kind of guy... don't know how the best single-user solution would scale for your purposes.
Yes you can... documentation says disk size can be up to 32 GB on Fat32 (max file size 4 GB). Win98 boot disk is my diagnostic platform of choice as well. If for some reason this doesn't work, I would try the disk utility in Linux. If you don't have graphical Linux available, use gparted. So much fun.
So i set up a L2TP/ipsec VPN server on my mac running 10.6.x. I can connect to the VPN from my LAN, but not from outside of it. This is from my HTC evo. I set up a VPN server using a virtual machine of 10.6.x Server, with the same results (can connect inside LAN, but not outside). Not that it makes any difference, but I can't connect either when I'm on my LAN but going outside my LAN and coming back (that is, the destination address isn't a local private address but rather my WAN IP address).
I have a Linksys E2100L router -> i'm pretty sure it's not the problem. I started by forwarding ports 500, 1701 and 4500 to the desired VPN server. When that didn't work, I forwarded literally every port to the server. Still failed. VPN passthrough is enabled on the router.
I have the ability to set up a linux box as a packet sniffing bridge (to see what traffic is actually making it back to my WAN IP), but I think the answer has to be simpler than all of the work that would take.
I don't have another device available right now to try to connect to my VPN from outside the LAN, but since the connection worked from inside my my LAN, I imagine that it should work anywhere.
I did do some packet sniffing of successful VPN connections to each of my servers, and of unsuccessful ones. That info is ...
if you want to compare, look at their 1) throughput, 2) seek time, and 3) access time.
If you're concerned with speed... get 2 7200 RPM drives and hook them up in raid 1. Or get 4 and hook them up in Raid 10 (for a bigger drive). IMO, spending money for fast platter drives is a waste, and spending money on SSDs is a waste right now, because prices will come down soon. the cheap ones are too small to make use of, and the big ones are too expensive to justify for the non-wealthy consumer. if money is no object, get some gorgeous big SSD's and watch them fly.
that looks like it might be a similar issue. resolution might be similar. that is a canon printer they're talking about though, so don't try the exact same thing, of course... :-P