Avali Nexus

Full Version: Avali Nexus Forum Thread: 4 Score and Several Threads Ago...
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
(06-02-2016, 03:34 AM)SilverOtter Wrote: [ -> ]
(06-02-2016, 02:59 AM)Shaadaris Wrote: [ -> ]I FELT LIKE I WAS GOING TO BREAK SOMETHING THE WHOLE TIME I WAS TYPING THINGS IN AAAAA.
You know, this is exactly why so many people are purposefully tech illiterate.

I just try to avoid messing with the command prompt because I don't quite understand the workings of it. I don't actually think it's that easy to break everything in the CP. If anything, it'd just spit out error messages since I don't know how its syntax works in the first place.
I'd be worried too computers and software are so fickle and hard to read and they can fuck themselves almost irreversibly at the drop of a hat with ZERO provocation. I can't recall the last time something went seriously wrong with my computer or any computer I was using that made an ounce of sense in symptom, cause, or solution.
(06-02-2016, 03:48 AM)Surge Wrote: [ -> ]I'd be worried too computers and software are so fickle and hard to read and they can fuck themselves almost irreversibly at the drop of a hat with ZERO provocation. I can't recall the last time something went seriously wrong with my computer or any computer I was using that made an ounce of sense in symptom, cause, or solution.

Very rarely do I actually have something bad happen to my computers. I think over the course of the 3 computers I've owned over the course of probably around 10 years, I've had MAYBE a grand total of 20 crashes/bluescreens/freezes, all of which were fixed by turning it off and on again (hey, it's actually good advice, go figure).
Of course, I've never customized any of my computers' hardware, nor have I tried overclocking, and I'm generally pretty good at keeping the software side of things running smooth by not downloading anything suspicious, regular disk cleaning and defrag, etc.

To put it into perspective, less than half of those crashes were on my first computer, which was a very weak, pretty sure 32 bit Vista, small laptop. It ran decently well while I used it. I somehow got a Vista computer to work decent for like 3-5 years... And when it finally failed, it was the screen that gave out (specifically, the hardware responsible for making the screen dark when it goes to sleep broke and the monitor was perma-dark.)
My Dad "fixed" it (i.e. cut the wire responsible, which is now sticking out of the side of the computer), formatted the thing after I got my stuff off to my 2nd computer, installed Windows 7, and gave it to my Mom... She still uses it. It's like... potentially a decade old.

So it always confuses me when people seem to have a bunch of major problems with their computers. Maybe I'm just lucky or something. The only problem I currently have is that on my 2nd computer, a Win7 laptop, the anti-hacking addon for MMOs GameGuard will cause it to bluescreen without fail when I try to play certain games... Which I STILL have no idea what the cause of is... It used to work.
(06-02-2016, 03:48 AM)Surge Wrote: [ -> ]I'd be worried too computers and software are so fickle and hard to read and they can fuck themselves almost irreversibly at the drop of a hat with ZERO provocation. I can't recall the last time something went seriously wrong with my computer or any computer I was using that made an ounce of sense in symptom, cause, or solution.

Every computer error I've had has generally made sense. I suppose it would seem that way if you weren't very familiar with the workings of a computer but computers are hardly unreliable - most modern software is super recoverable. It's usually quite difficult to actually fuck something up really badly.
(06-02-2016, 04:08 AM)Segolia Wrote: [ -> ]
(06-02-2016, 03:48 AM)Surge Wrote: [ -> ]I'd be worried too computers and software are so fickle and hard to read and they can fuck themselves almost irreversibly at the drop of a hat with ZERO provocation. I can't recall the last time something went seriously wrong with my computer or any computer I was using that made an ounce of sense in symptom, cause, or solution.

Every computer error I've had has generally made sense. I suppose it would seem that way if you weren't very familiar with the workings of a computer but computers are hardly unreliable - most modern software is super recoverable. It's usually quite difficult to actually fuck something up really badly.
Yes crash messages from perfectly fine up to date drivers 30+ times a day made perfect sense, the PSU that could make a determined attempt to light itself on fire in mere seconds but couldn't actually power anything was absolutely logical, the abrupt total failure of msconfig after Windows explorer irretrievably locked up is such a simple problem, and how I could forget how trivial that time my BIOS suddenly tried AND ALMOST SUCCEEDED to boot Windows via a wireless USB receiver was.
Computers seem to be far more prone to doing weird shit around me in some bizarre reverse Midas touch but that doesn't change the fact that they do weird shit.
Yes it is a bit of a sore point because I have to deal with the expensive and stressful consequences of this inane nonsense far more often than I would like, and it is rather difficult to diagnose many of these problems when the troubleshooting software is uncooperative or the backup components duplicate only some of the symptoms of failure and just further complicate the whole process.
(06-02-2016, 03:45 AM)Shaadaris Wrote: [ -> ]
(06-02-2016, 03:34 AM)SilverOtter Wrote: [ -> ]You know, this is exactly why so many people are purposefully tech illiterate.

I just try to avoid messing with the command prompt because I don't quite understand the workings of it. I don't actually think it's that easy to break everything in the CP. If anything, it'd just spit out error messages since I don't know how its syntax works in the first place.
Windows Command Prompt is just weird, but that's my opinion. Getting to know the command line usually opens up quite a bit of understanding of an OS on other platforms, but since NT Windows doesn't want anything to do with the command prompt, it's not central knowledge. Honestly, the only thing useful there is ipconfig and ping.

So the problem here is that you don't want stuff to break, because you don't have enough knowledge about the computer. Unfortunately, you don't learn how computers work without messing around with them and learning from failures. I had to learn to double-check dangerous commands once, and never needed another lesson.
(06-02-2016, 03:48 AM)Surge Wrote: [ -> ]I'd be worried too computers and software are so fickle and hard to read and they can fuck themselves almost irreversibly at the drop of a hat with ZERO provocation. I can't recall the last time something went seriously wrong with my computer or any computer I was using that made an ounce of sense in symptom, cause, or solution.
Hey, it used to be worse. Back in the old days, if you were missing even a sliver of understanding of the computer, you'd brick $5000 worth of electronics that belonged to a company.
(06-02-2016, 04:16 AM)Surge Wrote: [ -> ]
(06-02-2016, 04:08 AM)Segolia Wrote: [ -> ]Every computer error I've had has generally made sense. I suppose it would seem that way if you weren't very familiar with the workings of a computer but computers are hardly unreliable - most modern software is super recoverable. It's usually quite difficult to actually fuck something up really badly.
Yes crash messages from perfectly fine up to date drivers 30+ times a day made perfect sense, the PSU that could make a determined attempt to light itself on fire in mere seconds but couldn't actually power anything was absolutely logical, the abrupt total failure of msconfig after Windows explorer irretrievably locked up is such a simple problem, and how I could forget how trivial that time my BIOS suddenly tried AND ALMOST SUCCEEDED to boot Windows via a wireless USB receiver was.
Computers seem to be far more prone to doing weird shit around me in some bizarre reverse Midas touch but that doesn't change the fact that they do weird shit.
Yes it is a bit of a sore point because I have to deal with the expensive and stressful consequences of this inane nonsense far more often than I would like, and it is rather difficult to diagnose many of these problems when the troubleshooting software is uncooperative or the backup components duplicate only some of the symptoms of failure and just further complicate the whole process.

There's a trope for your ailment.
http://tvtropes.org/pmwiki/pmwiki.php/Main/WalkingTechbane
Alternatively, everything you work with might happen to coincidentally be
http://tvtropes.org/pmwiki/pmwiki.php/Main/TheAllegedComputer
Shaadaris: Only the most useless commentary
(06-02-2016, 04:16 AM)Surge Wrote: [ -> ]
(06-02-2016, 04:08 AM)Segolia Wrote: [ -> ]Every computer error I've had has generally made sense. I suppose it would seem that way if you weren't very familiar with the workings of a computer but computers are hardly unreliable - most modern software is super recoverable. It's usually quite difficult to actually fuck something up really badly.
Yes crash messages from perfectly fine up to date drivers 30+ times a day made perfect sense, the PSU that could make a determined attempt to light itself on fire in mere seconds but couldn't actually power anything was absolutely logical, the abrupt total failure of msconfig after Windows explorer irretrievably locked up is such a simple problem, and how I could forget how trivial that time my BIOS suddenly tried AND ALMOST SUCCEEDED to boot Windows via a wireless USB receiver was.
The updated driver had a bug, the PSU was either cheap or faulty, Windows, just Windows (why have failures be your fault, when we can do it for you!), and something set the BIOS to Netboot (which does work over Wi-Fi if the motherboard loads the drivers involved).
(06-02-2016, 04:26 AM)SilverOtter Wrote: [ -> ]
(06-02-2016, 04:16 AM)Surge Wrote: [ -> ]Yes crash messages from perfectly fine up to date drivers 30+ times a day made perfect sense, the PSU that could make a determined attempt to light itself on fire in mere seconds but couldn't actually power anything was absolutely logical, the abrupt total failure of msconfig after Windows explorer irretrievably locked up is such a simple problem, and how I could forget how trivial that time my BIOS suddenly tried AND ALMOST SUCCEEDED to boot Windows via a wireless USB receiver was.
The driver had a bug, the PSU was either cheap or faulty, Windows, just Windows (why have failures be your fault, when we can do it for you!), and something set the BIOS to Netboot (which does work over Wi-Fi if the motherboard loads the drivers involved).

The drivers issue persisted for MONTHS across multiple versions and installs of the drivers until I outright replaced the hardware. Yes I am currently in the process of replacing that PSU right now because it has obviously burned itself out. FUCK Windows errors. That happened to me TWICE and I still don't understand how or why, just that it was annoying as hell to right and one time it actually managed to boot into an unauthorized version of Windows.
(06-02-2016, 04:29 AM)Surge Wrote: [ -> ]
(06-02-2016, 04:26 AM)SilverOtter Wrote: [ -> ]The driver had a bug, the PSU was either cheap or faulty, Windows, just Windows (why have failures be your fault, when we can do it for you!), and something set the BIOS to Netboot (which does work over Wi-Fi if the motherboard loads the drivers involved).

The drivers issue persisted for MONTHS across multiple versions and installs of the drivers until I outright replaced the hardware. Yes I am currently in the process of replacing that PSU right now because it has obviously burned itself out. FUCK Windows errors. That happened to me TWICE and I still don't understand how or why, just that it was annoying as hell to right and one time it actually managed to boot into an unauthorized version of Windows.
Well then it's a hardware issue. Sometimes small damage to the card won't completely destroy all it's functionality, but it will cause the driver to report every chance it gets that a graphics extension that SHOULD be working isn't.

Also, that netboot problem sounds like you've got something configured on the network that is mistakenly being recognized as a windows netboot server.
(06-02-2016, 04:57 AM)SilverOtter Wrote: [ -> ]
(06-02-2016, 04:29 AM)Surge Wrote: [ -> ]The drivers issue persisted for MONTHS across multiple versions and installs of the drivers until I outright replaced the hardware. Yes I am currently in the process of replacing that PSU right now because it has obviously burned itself out. FUCK Windows errors. That happened to me TWICE and I still don't understand how or why, just that it was annoying as hell to right and one time it actually managed to boot into an unauthorized version of Windows.
Well then it's a hardware issue. Sometimes small damage to the card won't completely destroy all it's functionality, but it will cause the driver to report every chance it gets that a graphics extension that SHOULD be working isn't.

Also, that netboot problem sounds like you've got something configured on the network that is mistakenly being recognized as a windows netboot server.
I still fail to see how netboot was convincing the BIOS to boot via the receiver for my wireless keyboard.
(06-02-2016, 05:00 AM)Surge Wrote: [ -> ]
(06-02-2016, 04:57 AM)SilverOtter Wrote: [ -> ]Well then it's a hardware issue. Sometimes small damage to the card won't completely destroy all it's functionality, but it will cause the driver to report every chance it gets that a graphics extension that SHOULD be working isn't.

Also, that netboot problem sounds like you've got something configured on the network that is mistakenly being recognized as a windows netboot server.
I still fail to see how netboot was convincing the BIOS to boot via the receiver for my wireless keyboard.
Possible explanation: If you have no other devices in the network, it was likely trying to boot off of ITSELF.

Netboot is just a mode of booting up the OS, only across a network. If the BIOS is set up in some way, attempting a Netboot will come first before scanning the hard drives for a local OS.
(06-02-2016, 05:03 AM)SilverOtter Wrote: [ -> ]
(06-02-2016, 05:00 AM)Surge Wrote: [ -> ]I still fail to see how netboot was convincing the BIOS to boot via the receiver for my wireless keyboard.
Possible explanation: If you have no other devices in the network, it was likely trying to boot off of ITSELF.

Netboot is just a mode of booting up the OS, only across a network. If the BIOS is set up in some way, attempting a Netboot will come first before scanning the hard drives for a local OS.
Do legacy BIOS boards even support that?
Augh darnit I just had to go and get used to my laptop's 1366x768 resolution...
Now I'm trying to play Terraria on my 1600x900 Desktop and I can't get a resolution I'm happy with...
1280x720 is what I used to use on both... But now it feels too blurry and enlarged.
1366x768 works on this monitor but it puts black bars at the top and bottom (ech, this isn't a cinematic experience I want. I have pixels. Use them!)
1440x900 looks okay and runs decently, I guess, but I think it might look a bit stretched. It's hard to tell but it's a tad annoying.
and of course, my native resolution for this one, 1600x900, looks crisp and wonderful but extends my view more than I'd like and doesn't run well because apparently Terraria must be graphically intensive and I somehow didn't notice...
This is the problem with pixel-art games. Stuff like this is more noticable. Bleh.
(06-02-2016, 05:11 AM)Surge Wrote: [ -> ]
(06-02-2016, 05:03 AM)SilverOtter Wrote: [ -> ]Possible explanation: If you have no other devices in the network, it was likely trying to boot off of ITSELF.

Netboot is just a mode of booting up the OS, only across a network. If the BIOS is set up in some way, attempting a Netboot will come first before scanning the hard drives for a local OS.
Do legacy BIOS boards even support that?
Netboot has been with computers for decades.
(06-02-2016, 04:16 AM)Surge Wrote: [ -> ]
(06-02-2016, 04:08 AM)Segolia Wrote: [ -> ]Every computer error I've had has generally made sense. I suppose it would seem that way if you weren't very familiar with the workings of a computer but computers are hardly unreliable - most modern software is super recoverable. It's usually quite difficult to actually fuck something up really badly.
Yes crash messages from perfectly fine up to date drivers 30+ times a day made perfect sense, the PSU that could make a determined attempt to light itself on fire in mere seconds but couldn't actually power anything was absolutely logical, the abrupt total failure of msconfig after Windows explorer irretrievably locked up is such a simple problem, and how I could forget how trivial that time my BIOS suddenly tried AND ALMOST SUCCEEDED to boot Windows via a wireless USB receiver was.
Computers seem to be far more prone to doing weird shit around me in some bizarre reverse Midas touch but that doesn't change the fact that they do weird shit.
Yes it is a bit of a sore point because I have to deal with the expensive and stressful consequences of this inane nonsense far more often than I would like, and it is rather difficult to diagnose many of these problems when the troubleshooting software is uncooperative or the backup components duplicate only some of the symptoms of failure and just further complicate the whole process.
I had a friend who actually hacked his mouse to be a Linux boot disc.

So it can happen, dunno why the mouse had gigabytes of storage though.

Also I found a 64 megabyte flash drive, damn this thing is useless.
(06-02-2016, 02:45 AM)Ehksidian Wrote: [ -> ]
(06-02-2016, 02:22 AM)Surge Wrote: [ -> ]BLOOD FOR THE BLOOD GOD, SKULLS FOR THE SKULL THRONE!

milk for the khorne flakes?

And ear plugs for the next time slaanesh uses his axe for personal reasons.
*detracked a C1 Ariete*
*charge ram attack against the C1 Ariete*
*destroyed self on impact*



you see Ivan, when you're drunk in the battlefield, the germans cant hit you, because they think you're drunk and need to go home

https://gma.yahoo.com/north-korean-newspaper-endorses-wise-donald-trump-over-165504182.html
..........huh............
It's noon and my guaranteed delivery PSU isn't here yet aaaaaaaaaa