Yeah, it’s a fragile process indeed when considering all possible quirks
Is there any way you could post exactly what a correct load screen looks like for the senior and junior. There are lots of numbers in addition to just the name of the version at the top
Thanks Ted, sorry I guess I never knew if what people posted were for sure the right ones.
No problem, I just didn’t have the DS nor Jr in my system right now.
1 Like
I still believe memory dumps would reveal:
- If there are differences at all.
- If there are differences, WHAT/WHERE are those differences.
One could take a “pristine/virgin” Sr/Jr, do a load, and look at what is stored.
Take an exsisting Sr/Jr with a previous version, do a load, and compare it to the pristine/virgin load.
When someone is reporting a problem, it can be compared with the “known good” to see how/where there are variations/problems.
…waiting for the jokes about ‘virgin’ and ‘load’ now…
No, we’re better than that. This isn’t ASR.
2 Likes
i actually think some of the jokes are pretty funny though.
I don’t know if this counts as a technical problem but I encountered something strange while downgrading from Windom to Snowmass 3.0.0 and back to Windom again. For the record, i have never encountered any issues with upgrades to the DS firmware previously.
I usually and in all prior occasions, use(d) a SD card writer in a Windows PC. This time, I inserted the same SD card into an iMac SD slot. I didn’t format the SD card as it mounted on my Mac but just erased the files on it. I then copied the unzipped Windom files from my iMac to the SD card. It installed fine.
I also copied the same files into a folder on my PC subsequently using a SMB network share.
When I tried reinstalling Windom, I tried to copy the same files from the PC onto the SD card. However, I had a warning to the effect of:
Are you sure you want to copy this file without its properties?
The file has properties that can’t be copied to the new location.
I didn’t want to risk bricking the DS so I declined and just reformatted the SD card in Windows to FAT (it was originally in FAT anyway) and started afresh with new unzipped Windom files on the PC. Everything went without a hitch.
What is the error I got and why? They were literally the same Windom files unzipped on a Mac and copied to a PC.
Is the SMB share filesystem NTFS? If so, NTFS has some metadata (file permissions is one example) these aren’t supported on FAT or FAT32 file system.
No worries, the files are still the same, they just don’t contain any of the NTFS metadata.
Yes, the PC drive is NTFS formatted. But it has always been and I haven’t seen the error message previously copying files to the same SD card. When I unzipped the same Windom zip file downloaded from PS Audio, the files copied to the SD card without that warning.
Did the problem occur because I transferred them from Mac OS?
I guess it’s just academic anyway as you say the resultant files are the same anyway.
That’s all I use and I have never had a problem upgrading my DirectStream. But, my SD card is formatted to fat16…
As I assume you took care for Ted‘s to do list during your previous 20+ loads, it’s really crazy that this can happen…and why do others never have bad loads? That’s strange.
Ah, pleasing your wife and doing things together is the best you can do !
I wish you a good time.
In case you have done this before and it didn’t work i suggest : start with loading Yale first, followed by …
Yes - followed all procedures, did the additional boot without card, rolled back to two different old FWs - never sounded different. This time I was listening and noting bad recordings sounding funky, while good ones were quite good. Put on the new Robbie Roberston album on Qobuz, and when Van Morrison started singing in the first track, I thought, “This can’t be right”…it just sounded off. Was going to go back to Snowmass and realized I had not done the reboot without card this time, so did it. Completely different sound - basically what everyone has been talking about.
Still need to try it back in the main system, but both enjoying it too much and a bit scared it’ll go away when I unplug the thing. But it shouldn’t, as it is in there - it won’t be a reload.
BTW - almost never had any load problems whatsoever with the Jr. This is with a new Sr. And of course we’re not talking whether it says the correct FW name and numbers, but how it sounds.
Or maybe the DSD just Broke In… ; )
2 Likes
Wow! Your patience and diligence has been rewarded. 
crazy that you had to put in all that effort. 
Its a head-scratcher for sure.
May the force be with you!
1 Like
@Paul Long, long ago, in a galaxy far, far away (way earlier in this thread), our intrepid @tedsmith intimated that this “good load”/ “bad load” issue is well known to PSA but that you have chosen to not make its fix a priority for your engineering team. When pressed, Ted said to “ask Paul”.
Paul, given the ridiculous hoops many have gone through to acquire a “good load” of Windom, would you please share your plan for committing to solve this annoying and overwhelmingly documented bug. High end, very expensive DACs ought not be such a voodoo science to update.
Thanks 
1 Like
Go away. You are sickly. What did you leave me in the will?? 
I’ll read on - it will be interesting how you arrived at it…