New
#201
Not going to bother with the DX58SO anymore
Just installed 17063 on this silly little laptop and its all working fine
Not going to bother with the DX58SO anymore
Just installed 17063 on this silly little laptop and its all working fine
Understandable. It's the same logic that has kept me from upgrading my machine - everything still works.
The thought of upgrading the DX58SO hadn’t even entered my mind before the RS-4 release, why would it when the system has been working perfect and very responsive.
I remember before I updated the BIOS there were a lot more options in it; I’m going to downgrade to an older BIOS see what other options there are
I’ve tried a bootable Setup 17063 on a USB with a bios downgrade dated 05-16-11, 05-29-12, and 07-29-13, each time with the same result, cant boot from USB
Yet we know changing just the install.wim from a 16299 sources on to 17063 sources and it boots each and every time up to a point.
And we know that every RS-4 bootable USB boots and installs with the little old laptop successfully every time
So the conclusion has to be as we have said from the beginning, MS has changed some drivers in the RS-4s, making this Intel DX58SO motherboard incompatible with it.
Well, technically you can say that only if you try multiple HDs and rule out the HDs themselves.
But, hey, at least you're getting a modern system out of it :)
Costing an arm and a leg so far
Just the motherboard left to buy
That’s if we can salvage some of the DX58SO systems existing parts
Cooler Master Cosmos S ATX Full Tower Case – existing
BFG ES Series 800W PSU - existing
DELL 2407WFP – existing
Maxtor 6L300S0 ATA Device 300GB – existing
Western Digital WD Green 1TB – existing
New
Intel Core i7-8700K
Thermaltake RGB Fan 360 mm Water Cooling System CPU Cooler with Radiator
G.Skill Trident Z RGB DDR4 3600MHZ CL16 - 16GB (2x8GB)
Asus Rog Strix gtx 1060 6gb – second hand but sealed box
That is how I do builds - in 2008 I started my Core2Quad 6600-based machine, using pretty much all new stuff. When lightning took it out 3 years later (the PSU and HDs, but the mobo was flaky at best after the hit) I started the build I am on now, recycling the video cards, monitors, but going with a new case, CPU, mobo, RAM, PSU, and adding a Blu_ray burner. Since then, I've added HD storage space (added an 80 GB SSD, then a 240 GB SSD, then a 256 GB SSD, and finally a 960 GB SSD), replaced video cards (started with a pair of GTX 260s, added a GTS 250 for PhysX while using SLI on the pair, then added a GTX 560 Ti 448 core (removing one of the 260s plus the 250, using the remaining 260 for PhysX), then added a GTX 970, relegating the 560 to PhysX and removing the old 260), replaced both monitors with another matched pair, and ....I think that covers most of the 'upgrades' lol.
Pretty happy with the setup as is, as long as it works, but if I were to do a new build, at this point it would be just mobo, CPU and RAM, keeping everything else (and perhaps replacing the PSU, but if it will work with hte new components I will hold off on it).
Wonderful memory you have mate, my memory is not that good but the first and last (new) computer I ever bought was a 386 and I’ve been building them as and when I’ve needed to ever since.
While I was in the loft the other day I brought down this beauty (picture below) and it still works.
Wonder if it’s worth anything:)
All the telemetry MS have been getting with every unsuccessful upgrade I’ve tried on this system, maybe they will see the problem and resolve it in the future sometime. :)
From:
C:\Windows\Panther\NewOs\Panther\setupact
2017-12-28 17:15:48, Info Copy telemetry file: source folder: C:\$Windows.~WS\Sources\Panther, destination folder: C:\ProgramData\Microsoft\Diagnosis\ETLLogs
2017-12-28 17:15:48, Info Copy etl files: source: C:\$Windows.~WS\Sources\Panther\DlTel-Merge.etl, destination: C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl
2017-12-28 17:15:48, Info pCopyTelemetryFile: Wrote CV elCeJxrqokSbncnk.2 to ETL C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl:$ETLUNIQUECVDATA
2017-12-28 17:15:48, Info Diagtrack service is running
2017-12-28 17:15:49, Info Successfully Forceuploaded the telemetry data.
2017-12-28 17:15:49, Info Upload files successfully so we can remove all etl files.
2017-12-28 17:15:49, Info SP Closing Panther Logging
Doubt it - if they are blocking your hardware, they are doing it for a reason. Which, in M$ speak, means they've already fixed the bigger problem by creating your smaller problem. Lol.