https://www.youtube.com/watch?v=bWMGfFHr1ww
Printable View
Today I learned:
- before you install the motherboard usb drivers, the usb ports will only supply half or less of the required power to all devices
- printer drivers require better connectivity than printing operations: a 3m USB cable will work for printing but not for driver installation
- you can never uninstall a driver in windows. once it's installed, it's there --nothing you can do will uninstall it
- laser printers cannot print borderless
When buying a printer, test with these margins tests. It'll save you a lot of headaches in the long run:
Attachment 17858
I learned that system restore doesn't bring you deleted files back. Now that I think about it, I should've know this.... :eek:
Today i learned that:
- Windows 10 cannot assign a page file to drives that have the letters A: or B: .
If you try you get the un-intuitive error:
Windows created a temporary paging file on your computer beause of a problem that occurred with your paging file configuration when you started your computer. The total paging file size for all disk drives may be somewhat larger than the size you specified.
Attachment 17891
- Windows installed in a VHD cannot have the page file in that same VHD.
DIE MS!!!
And if you want to use the kind of removable storage that would normally be assigned drive letters, you must download and install the driver manually #seriouslymicrosoftQuote:
Originally Posted by Master Razor
At least that error message gives you a hint. "A device attached to the system is not functioning" is far worse.
A Windows OS can only run for about ~80 days without crashing. I used to test this on my torrent servers. It was automated to restart the system every 80 days.
This pic is from 2/27/2017 11:26 , the last day before I took down the servers.
Attachment 17923
Turns out Excel 2013 has 3 formats of CSV files: Windows, Unix, and a REAL csv.
And this very old issue, the infamous SLYK file: Excel CSV import returns an SYLK file format error - Alun Rowe
The key here is: never start a CSV file with the word "ID".
i used to leave the computer on 24/7 while on win xp, afaik it did work for more than 2 months in one session, with torrents running 24/7 and heavy usage in between - seems with a lower usage it should be able to run much longer than just 80 days in a session.Quote:
Originally Posted by Master Razor
ufockingwotm8 :doge:Quote:
Originally Posted by Master Razor
Here's a screenshot from a Windows Server 2003 machine still running after a thousand days.
http://www.sb-innovation.de/attachme...chmentid=17961
What does this mean?Quote:
ufockingwotm8
A server is not the same thing as a consumer OS. I was using windows 7 at the time.Quote:
Here's a screenshot from a Windows Server 2003 machine still running after a thousand days.
I don't think I can get very technical here but I'll try: When you set in windows power settings high-performance, and never shutdown disks, monitors, etc, it only stays up when the os is actually being used. Even though everything stays up, the system over time will get slower and slower and only the most recent performed functions will work. Massive timeouts to system calls and other functions will eventually lead to crashing. I've seen this happen before. Not exactly sure if it's 80 days but that's my safe limit based on my experience.Quote:
i used to leave the computer on 24/7 while on win xp, afaik it did work for more than 2 months in one session, with torrents running 24/7 and heavy usage in between - seems with a lower usage it should be able to run much longer than just 80 days in a session.
u-focking-wot-m8, as in 'what did you just say/do, mate?'Quote:
Originally Posted by Master Razor
Code:http://www.urbandictionary.com/define.php?term=U%20Wot%20M8
okQuote:
that's my safe limit based on my experience.
I can't relate to this, I've ran Windows 7 for months and only noticed glitches at worst (which go away by refreshing or reopening a dialog).
http://68.media.tumblr.com/a7a9cc01c...s4so1_1280.gif
http://68.media.tumblr.com/f74aa8116...s4so1_1280.png
I'm not saying it can't happen, as it obviously does for you, but this may hardware, driver or setup dependent, rather than a problem with Windows per se.
Today i learned that a network bridge via software (windows os settings) will slow down copy operations by 80%.
6.000 files/1GB copied in 2 hours
outside of bridge: 2 minutes
I used a USB to ethernet adapter to create the bridge. USB port used was 3.0 and ethernet was 1GB.
the usb adapter works fine, as long as it's not in a bridge.
Today I learned that stopping the WLAN Autoconfig service or running the following command can prevent lag spikes on wireless connections, by stopping Windows from managing them. However, that means it won't reassociate on connection loss or see any networks at all, so you'd have to toggle it constantly.
For some adapters you can instead control this behavior from the Device Manager in a less compromising manner. Enable gaming mode/QoS/SmartScan, disable background scanning, and/or set the roaming sensitivity to disabled.Code:netsh wlan set autoconfig interface="Wi-Fi Adapter Name Here" enabled=no
rem Set "enabled" to yes to undo this
Today I learned that when copying drive roots with robocopy, the resulting destination is set a hidden attribute.
Hidden and system. Also, if you choose to copy directory timestamps, the destination's is set to New Year 1980 for FAT volumes, and the volume creation date for NTFS.Quote:
Originally Posted by Master Razor
Windows 10 ISOs are now over 5GB which means only Dual Layer DVDs will work from now on for both BIOS and UEFI. Rufus will not be able to make a UEFI usb stick from them because UEFI only supports fat32, and the iso, and biggest file in the iso is over 4GB. Once again: FUCK MICROSOFT!!!
why not just use a larger sized USB stick and format it ntfs?Quote:
Originally Posted by Master Razor
Because: UEFI only supports fat32
"Official system requirements were an Intel 80386DX CPU of any speed, 4 MB of system RAM and 50-55 MB of hard disk space depending on features selected."
Today i learned that there is no DVD+/-RW DL. This is really bringing me down...
Today i learned that microsoft decided to remove the file diskcopy.dll which is actually an image of MS-DOS 8.0/WinME crippled MS-DOS. Which of course the popular program Rufus was based on to create MS-DOS usb sticks. Now, if you're using Rufus on any other OS except 10, it will work fine, but on 10 you can only use FreeDOS.
PS: People that say FreeDOS is better than MS-DOS have no ideea what they are talking about.
Faux Bold and Italic Typefaces:
https://www.marksimonson.com/noteboo...evsTrueItalics
Everything done b y microsoft is fake, fake to the core! Not even the fonts are real.
I used to resent Windows ME for removing access to DOS and real mode, but then I learned it was done to reduce boot times and make the system more stable (or less unstable, depending on how you see it). It also had other improvements like Windows Image Acquisition, HLTing the processor when idle, and the Windows 2000 TCP/IP stack. System Restore and file protection were also good ideas, they just weren't implemented well (perhaps due to the limitations of the FAT32 file system).Quote:
Originally Posted by Master Razor
Anyway, I didn't learn this today, but hopefully it still counts :cylon:
%windir%\System32\DriverStore\infpub.dat
%windir%\System32\DriverStore\infstrng.dat
%windir%\System32\DriverStore\INFCACHE.1
%windir%\System32\DriverStore\infstor.dat
%windir%\System32\DriverStore\drvindex.dat
Those files are very important and should never be deleted, no matter what anyone tells you. Doing that breaks automatic driver installation... forever, if you don't have a backup. I was not aware of this, and the only solution I knew was reinstalling Windows. It started happening once more this week; after cross-checking directory and registry key timestamps and trying different things, I realized that all this time I'd made things worse by deleting the driver cache at some point.
Restoring those files from a system backup made the previous week fixed it immediately, without even needing to reboot.
Today I learned what is "Windows Modules Installer Worker” and what is does! So basically it is installing updates in the back ground. I kill it every time it runs on Windows XP professional as it keeps warning me about some of the softwares and modules I have on my pc. I choose to install updates manually. However, I despise this "Installer".
You need to grab an untouched ISO of Windows XP SP3 and all its updates from Microsoft, then use nLite to integrate the latter and remove Automatic Updates, the Security Center and all that jazz. XP support ended three years ago, so there is no reason for it to check for updates anymore. On exceptional circumstances like the Internet Explorer 8 and ransomware vulnerabilities, just download and install the fixes yourself.
I did this for my desktop computer, except that it was with Windows Server 2003, and I went one step further and removed everything I didn't need (in addition to the removals and changes already necessary to turn a server OS into a workstation). The result was an install that uses just 500 MB of disk space and is super fast.
Since we're on the subject, what do you guys think of Maherz releases of Windows XP SP3? From here Windows XP Support
Are they any good?
I think I used their release a few time! Worked fine for me!
I used it a few times when I needed an XP that was updated but otherwise untouched. It delivered exactly as expected, although right now it's missing the update Microsoft posted a few months back to fix that ransomware vulnerability.
It's too bad simplix is not creating these packs for all other operating systems. At least XP and 7 should be updated.
@anon
What would be the best way to update XP? nLite to slipstream for sure but how do you get all the updates from SP3 until preset? I don't want t download them one by one...
Oops, I didn't notice this edit until now. The answer is nLite, of course. Just go to xdot.tk to get a batch file that downloads all updates released after Service Pack 3, then add all of them to your list of slipstreamed updates, sorted by KB number in ascending order.Quote:
Originally Posted by Master Razor
Today I learned that you can "[s]et up an environment variable called SSLKEYLOGFILE that points to a writable flat text file. Both Firefox and Chrome (relatively current versions) will look for the variable when they start up. If it exists, the browser will write the values used to generate TLS session keys out to that file."
As a coder, I am amazed at how much the dash character is used in naming filenames and naming language constructs such as classes, functions, variables... .
It is a know fact that the recommended delimiter is a underscore. Besides the aesthetics, it also treats multiple words as one (double-click selection). However, when used in webAPI, the delimiter should be a dash. Web crawllers indexes dashed words as separate words.
I have never named any file with a space or a dash. Always use underscore for everything.
Still I'd like to know why this is. Why does an OS treats lorem_ipsun as a whole while lorem-ipsun as separate? Is this an OS setting, a character set limitation/feature, or what?
I just found out that Windows 10 v1703 is the only version/edition of windows that supports RDNSS. The RFC was made in 2010 yet they implemented it in 2017, DIE MICROSOFT!!!! DIE!!
They also implemented a robust dual TCP/IP stack which was responsible for single-handedly increasing IPv6 adoption all around the world, and half a decade before that was trendy... but hey, fuck Microsoft, fuck the system :idunno:Quote:
Originally Posted by Master Razor
Note I'm not counting the IPv6 previews that were available for Windows XP, 2000 and even 98, because those were a mess.
Yes but you forgot to mention something: that was then, this is now. If you look closely, no RFCs are followed anymore by microsoft. There are huge delays in any implementation if any. Windows is a mess.Quote:
They also implemented a robust dual TCP/IP stack which was responsible for single-handedly increasing IPv6 adoption all around the world, and half a decade before that was trendy... but hey, fuck Microsoft, fuck the system
A long time ago I learned that windows create a separate boot partition 100mb/200/mb/350mb/whatever the fuck has w10 now... on any drive that doesn't have a active partition bit set. I other words, if you format the drive from the windows setup, and select install, it will always create a separate boot partition. The documentation of microsoft doesn't specify (what a shock) that this behaviour applies to unattened setups as well.
For instance, in a unattend.xml is set create partition 1 and partition 2. Now if you configure it to only create one partition and leave the rest unpartitioned, it will correctly use the C drive as boot and recovery. If you set it to create two partitions, it will set all your boot files on D drive.
Also learned that windows 10 security is severely crippled when installing updates. Most AV suites stop working (again, what a shock) when updating from a previous build to a newer one. Basically, anything that gets deep in windows and integrates with it, like an av for instance will not work correctly. So does large software suits such as adobe or autodesk. Performance issues all around.
And I also have a theory. I know that microsoft gives out parts of its windows source code to any country that refuses to use it unless is verified as safe. Now, the chinese and russians have had all windows source codes since the year 2000. The russians have control over the popular av suite kaspersky. Everything is tracked, either via microsoft or antiviruses. I suspect at the first sign of war many windows machines will stop working. A timebomb can come from anywhere.
That microsoft is so...
Today I learned that a remote desktop connection will automatically adjust to your main screen. If you want it to adjust to a different screen, you have to manually match the Display resolution in Display tab, Display Configuration to your monitor's display resolution. As far as I know, there is no other solution to this.
Enjoy! (!@#$! microsoft, can't do anything right)
So, I configured my self these, which you will find them in the attchment:
Attachment 18346
Today i learned that HDDs are not throughly tested using file copy or formats. Using these tests most HDDs survive but checksum operations will stress them out even more.
My 2 test scenarios are:
1. zero out format + copy 4GB+ files + 256SHA checksum each file and save result on hdd
2. same as above only with small 4K files
I can't prove it yet but I suspect those checksums killed 3 of my drives.
The result is HDTune test on all drives report 100% damaged blocks, on quick and full.
I don't have to test the obvious that these drives were new, right?
And if I had the money, I would sue each of these so-called garbage manufacturers.
I learned today that my Kingston DataTraveler G4 usb flash key is useless. It's suppose to be USB 3.0, but speed is slow as fuck!