When checking the “Windows” set of files, I noticed that the LOADER.CFG file appears to be a slightly earlier version (dated about a day earlier than the one in the original release).
Is there any significance to this in terms of ensuring a “good load” when a Windows machine was used to download and set up the SD card?
Not that I suspect I have a “bad load,” but Inquiring minds want to know 
The Mac version when ‘unpacked’ also has a slightly earlier version of the LOADER.CFG file as the original release and 7 minutes later as the (new) Windows version, the byte count of the three versions is the same. The other files have the same ‘timestamp’ as the original versions.
There’s a Windows utility called TeraCopy that does things like checking whether a transfer is an accurate copy. It’s free - read about below:
Nope. Just timing on when it was produced. Same code.
So, why do you produce the same code more then once ?
Ok, i updated my Ds again, this time with a balenaEtcher generated Windom SD card (on a Mac).
Coming from an already brilliant working Windom, the newly updated Windom sounds (as expected) exactly the same as the previous one.
It is very well possible that the balenaEtcher method is more robust in creating a good SD card.
At the other hand it creates FAT32 instead of FAT16.
I think some people are having problems with the update because of the SD file system format, I have not had any issues on any update of any versions, Here is some info on the exFAT vs FAT32 that could be an issue for some.
FAT32 is the most widely compatible file system. It will work on any operating system as well as video game consoles, Android USB expansions, media players, and other devices. In contrast, exFAT will work on 99 percent of the devices you use, but may not work on some media players and Android devices.Jun 14, 2017
Hey Jovo3!
It sounds like you either need a screen calibration, or you may be touching just to the left of the plus, which would activate a normal function of the unit (where you tap the volume you’d like to be at).
Turn off the unit with the rear switch and whilst holding the front logo button, turn the unit on with the rear switch. You’ll see a screen with a 1,2,3,4 in the corners. Follow the onscreen instructions and the unit will initialize.
Thanks!
My remark was about FAT16 not exFAT.
In the past PS Audio gave the advice to format to FAT16 instead of FAT32.
Now the new balenaEtcher method does format to FAT32.
Maybe more important is the usable size of the SD card after the balenaEtcher action, wich is very small (62.9 MB). Much smaller even as when formatted as FAT16 (2.15 GB).
Hi CustomerService,
Maybe i touched just left of the plus that made the DS run to 100.
The running to 100 happened somewhere to 1 out of 7.
If that’s a normal function then it’s a very dangerous one, you better limit that function to let’s say 80 maximum.
After recalibration the problem seems to be solved, thank you for the good advice !
Sorry, but that sounds like a bad load.
In my initial Windom load, there was too much grit, the highs were not sweet (compared to a good load), too much emphasis in the medium register and the sound was mainly encapsulated between the speakers: with a good Windom load, the sound extends well beyond the speakers.
How do you know if you have a bad load or a good load? if you have a bad load, how do you make it a good load?
Good question - badbeef and Paul say PSA are working on it - given that I have three dacs (active speakers) I need to know that they’re all doing the same thing - nobody seems to be able to tell us what’s going on.
The current SOTA is to download the Mac/Windows specific version from the Resources Page here on PS’s site, and follow the current instructions. I’m a Mac person, so that involves downloading the Etcher app and flashing your SD card (talking DSD here vs. Jr., which is USB drive). This ensures the card is erased and written properly, as that is a big source of bad loads.
(Dunno about Windows - others weigh in regarding that)
I am unsure if there is a comprehensive source/list for things to do physically. But from different sources/experiences, I would say that, before you Load that SD card or USB drive, you should:
Turn power off and let it sit for 3 minutes.
While power is off:
Remove any SD card or USB drive in the unit.
Disconnect any HDMI cables…hell, maybe ANY cables. Not sure. Cetainly digital and Ethernet/Bridge if you have it, cables. Analog likely doesn’t matter.
Did you wait 3 minutes?
Put the new card/drive in and turn power on. It should cause the Blue Light on the front to blink for a While, do not Worry about How Long that takes, then it will Initialize. That will also take a while, continue to not worry : )
Check the Version screen to confirm that the intended FW has actually loaded, rather than it still being the prior FW.
REMOVE the card or USB drive from the DS.
Turn the Power Off, wait a few seconds or so, and turn it back on. It should NOT Blink Blue, but should initialize. It should still be what you loaded previously.
Plug your digital sources back in. Confirm that they show up, or just set the DS to Auto input. Turn the volume up if necessary, as it may reset to 25 so you don’t blow your speakers up.
Check that Shiz out.
Honestly, I suspected I had a bad load by listening to it: it sounded terrible compared to Snowmass.
When you read on the forum all of the great attributes of Windom and it does not match what you are hearing, then you can suspect a bad load.
The recipe to get a good load has been abundantly discussed on this thread (.
Essential, you load an older firmware (like RedCloud) (remove SD card), re-boot, load Windom (remove SD card), re-boot.
Some others have gotten good results with Yale instead of RedCloud.
Not Essential for all, unless the Above process results in bad sound. Many go directly from prior FW to a Good Load of Windom. They tend not to complain. Or even post about it.
All of the descriptions of how to get a good load is another way of saying that there’s no empirical, scientific way to know if you have a good or bad load. Its a limitation of the DS/DSJ and while Paul and crew are aware of it, there has been nothing to suggest that fixing the issue is a significant priority. Ted has stated its beyond his field to solve the issue and that PSA is too busy with other engineering priorities. That’s simply what is. It’s a small company and I’m sure they are doing the best they can.
Stop making shiz up, man. You are reading into it and inventing.
All that I said is 100% true and documented… Ted said “ask Paul” and shared that fixing this issue is not a priority. If that has changed, great. But there has been no word from Paul to suggest it. They have only made the zip process better, but that’s not the same as being able to empirically tell if a load is good or not.
PSA is a great company. But they are not a perfect company and do have shortcomings. That’s not an insult, but rather a fact.
All you said is excerpted and interpreted by you as such. Ted and Paul don’t feel particularly compelled to respond to that, understandably, as you’ve demonstrated a tendency to be a Pot-Stirrer.