Jump to content

melkor

Atømican
  • Content Count

    142
  • Joined

  • Last visited

Everything posted by melkor

  1. Took this tonight, using a piece of colourful cardboard as a backdrop. Pretty happy with the results, pretty much straight out of camera - loaded into DPP, +3 sharpness, that's it. Exported to JPEG and uploaded to Flickr. No NR, contrast, hue/sat etc. No diffusion on flash either (built in flash on 60D). Dave
  2. melkor

    Yet another Blue Banded Bee shot

    During the day they are too busy flying around, and they fly much quicker than an ordinary Bee. If you have Blue or Blue coloured flowers in your gardens, then you'll most likely have Blue Banded Bees (they are attracted to the colour). Try very carefully searching in the garden on dusk where there are thin vines/plant stems/branches - no more than a metre high from the ground. You'll usually find a bunch of them too - the males are communal at night, even though these are classified as solitary Bees. As always, be careful when moving around in the garden - you don't want to hurt them. Remember the Golden rule of nature photography - the safety of the animals comes first Dave
  3. melkor

    Yet another Blue Banded Bee shot

    I was pretty happy how it turned out too. Dave
  4. And some legacy stuff. If you can get stuff like SW:KOTOR from 2003 running under W7 with compatability set to XP SP1.... I can only think Melkor has found native to show more stability than compatability or VM. Yes, true. I do like Doom 95 (hey, I"m from that era!!!) and Daggerfall from time to time. I'm not adverse to VMs either - I do actually use them. It's just nice to have a secondary physical operating system to go back to in event of a hardware failure with your primary drive o/s etc. Virtualisation itself is not a great form of redundancy from my experience, especially if a result of a hardware failure. I use vSphere and ESXi 5 and veeam 6 day to day in my work btw. I have another issue now, one that is perplexing but will post that in the Linux section. I was working on it late last night, on a tired brain, so will have another quick look at that problem tonight when I get home from work. Dave
  5. Hi Guys, Just finished my new PC build, pretty confident that everything is connected up as it should be. Parts: Gigabyte X79S-UP5-wifi motherboard Intel Core i7 3820 CPU Corsair 32GB (4x8GB) Vengeance CMZ32GX3M4X1866C10R DDR3 Red Samsung 840 pro 256GB SSD (sata 3) Samsung 840 120GB SSD (sata 3) WD 3TB 'green' SATA 2 drive Lian Li PC-A71F case Thermaltake Toughpower XT 875W PSU ODDs are a Pioneer Blu ray burner BDR-205 from memory) and a cheapie Samsung DVD burner. edit: I have a Creative Audigy X-treme pci soundcard in the new mb (cannibalised from my old PC) and I'm using a single Gigabyte Nvidia GT460 video card, also taken from my old PC. Both SSDs are connected to Sata 3 connectors on the mb. The ODDs and WD 3TB drive ar connected to SATA2 on the mb. RAM is seated firmly. CPU/FAN are AOK and seated properly. Now onto the problems. System boots up OK. I was using an old PS/2 keyboard and couldn't enter the bios, despite several reboot attempts. Tried tapping as well, no luck. Swapped the keyboard for a USB keyboard and could get into bios. All drives are detected, as is RAM. Everything looks OK to my eyes. Can't say that I'm a fan of the new style bios screens, prefer to k.i.s.s. I first tried Windows XP in the blu ray drive - the disc boots OK, does all the driver loading, goes to start Windows install and BSODs. Tried several times. I then tried to install Debian 'etch' (yeah, I know it's old, haven't bothered to download Debian 6 yet). Popped the Debian install DVD into the Pioneer drive, it does some detection and comes up with "no common drive detected". A bit of googling shows that this was a bug with some ODDs and Etch. I've never seen it before to be honest! In fact, I installed Etch on my old PC which I'm using now, using the very same Pioneer optical drive. Next step was to try setting the 2nd ODD (Samsung) as the main ODD boot drive and installing XP from that. Same BSOD. Tried Debian, same error as with the attempted install of Debian on the pioneer blue ray drive. My plan was: Samsung 840 120GB drive - Windows XP and Debian Samsung 840 pro 256gb drive Windows 7 x64 ultimate WD 3tb drive - data drive for my home folder for Windows 7 Nothing fancy. I've built like 6 systems since '97 and NEVER had so many problems as with this new system and I'm starting to become incredibly frustrated with it all. I've never had such errors before, and never had a failure installing an o/s of any choice (from Debian to freeBSD to Solaris to different Windows versions). I'm currently running memtest86+ from the Samsung drive and will let that run overnight, as some Googling after I'd already bought the RAM showed that there were issues with reliability with this particular ram stick - don't believe me, google it. I'll let this memtest run overnight. Still to try (tomorrow night now, giving what the current time is) - reset the CMOS, and check the current bios version and update it if necessary. I cannot see how even an older bios would have so many issues. That the bios is seeing all of the drives makes me confident that they're both connected up correctly from a data and power point of view. That I can boot from both XP and Debian CDs from both ODDs makes me also believe that they are connected up correctly. I will try installing Windows 7 on the Samsung 256GB drive tomorrow night just to see what it does - I expect it will error too. I'm at a loss to what's wrong and why I'm having these issues. Any suggestions or help appreciated. edit: the motherboard posts OK. Dave
  6. Well, the driver disk from Gigabyte explicitly says 32 bit folders for ahci, so I would have presumed that it was supported. I think some of the earlier versions of the driver from Intel were 32 bit, but then Intel changed its mind. I've come across several other people trying to get 32 bit XP installed on x79/c606 chipsets, so I'm not the only one. And yes, I tried nlite slipstreaming to no avail. Cool tool though (I'd never played with it before). I kept getting the iastorA.sys error during install. Said motherboard doesn't support a floppy disk drive, and XP doesn't support USB during install. I've actually given up on XP - it's silly that one can't choose to install their operating system, but I'm over it. Dave
  7. 1 more update - I have abandoned trying to get Windows XP 32 bit running in AHCI mode - it just is not do-able. Installs OK in IDE mode, but even then installing the drivers and rebooting and changing bios from IDE to AHCI gives you a BSOD. Since new motherboards stupidly lack support for a FDD, and Windows XP doesn't support USB sticks during install, it's a nogoer. Furthermore, I have tried to slipstream both SP3 and the 32 bit drivers for the C606 and Marvell chipsets for this motherboard without luck - it seems I get the infamous unable to find iastorA.sys error, despite loading the 32 bit drivers for AHCI via slipstreaming. It seems that I am not alone in this issue, and a few people have tried and given up. 1 German guy managed to get it going with a v3 irst driver that was modified by another user on the same forums, but the download links are all dead. It's simply not worth the hassle. From what I've been able to research, it seems that Intel does not support AHCI drivers for Windows XP 32 bit (but does for 64 bit) - stupid. That's like saying modern CPUs should be 64 bit only, and the modern operating systems should not support 32 bit applications. It's nice to see manufacturers remove our ability to exercise our rights to install software that we paid for. Furthermore reason for hating the proprietary computing systems that abound today. I'll go with Debian Squeeze on the 120gb SSD and Windows 7 on the 240GB SSD and have to live with that. I may do a virtualisation of XP on the Windows 7 platform at a later date, but it detracts from my original goals. That's it for my rant, thanks everyone for your help. Dave
  8. Just an update, I returned the original RAM (Umart gave me no problems) and got some slightly slower Corsair RAM (1600) instead. Tests perfectly fine in the new machine, not a single error. Haven't done much more with the system o/s wise. Dave
  9. melkor

    basketballfreak6's photos

    cooler weather, or early morning is the best time to shoot them as they are more inclined to stay still. After a few attempts, most of them will settle too and stop being fussed by you. As always, approach low, from the front, and slowly, with no noise. Excellent shot. Dave
  10. Well, have modified the RAM timings (never needed to do this before, so it's entirely alien and new to me - and I don't mind admitting intimidating). Couldn't find the north bridge memory controller voltage option, memory controller voltage (memory agent) as per description from Corsair. Anyone have an idea where they are and what they are called in the current Gigabyte UEFI bios? And, the testing with the modified settings as per Corsair (10/11/10/30, 1.65v for dram voltage, command rate 2T, memory set to 13.33 multiplier (i.e. 1333mhz)) isn't good - errors almost immediately, and errors where it wasn't erroring before. Not encouraging. I've opened a support ticket with Gigabyte last night, but haven't heard anything back from them. Modified that ticket just now to include the above question. I'll give them another 24 hours before I say enough is enough and return the RAM as faulty to the supplier. Which reminds me, I need to check Umart's RMA process. I don't want to stuff around, I simply want to return the RAM as faulty and get a replacement set (different ram). Anyone got experience with Umart's customer service/rma process? Dave
  11. Yes, I realise that XP 64 was not totally Microsoft's fault. But - Microsoft has a lot of pull in the industry, and they didn't exactly make much of an attempt to garner support from the rest of the industry. Plus, let's be very realistic here - very few people had 64 bit capable systems. At the time, Linux was also moving into 64 bit and provided a far more stable product too [than XP x64] imho. I've long argued the same reasons and defences in regards to GNU/Linux. I'm quite positive that if Microsoft ported MS Office to Linux (and it worked reliably) usage of the Windows Operating system would drop by a fair bit. Of course, we are now seeing this with OS X increasing it's market share (although I admit to disliking Apple far more than Microsoft to be entirely honest). Yes, I know updates are clearly defined as security and stability etc. My comments were a snide remark on proprietary software's attitudes of let's not support the product so we can force new dodgy software onto the masses ;-) And of course, make more money. Not quite true - the Linux kernel supports a very large amount of hardware, more so than Windows does out of the box. It's not bloated. Microsoft has long been renowned for writing bloatware. I'd hate to see Microsoft's hello world ;-) I'm a GNU/Linux guy at heart. I use Microsoft because in many instances, I'm forced to by proprietary software in order to get a particular thing done. If you'd read my various posts, you'd see that XP was there as far as I was concerned for backwards compatibility with older software applications, and also as a redundancy o/s on a physical disk, as opposed to a vm. A vm on my main system that has a hard drive fail is of no use to me. BTW, I don't dislike VMs, I use them on my MBP, and I use them at work day in and day out (I help maintain our servers, vmware infrastructure and veeam backups). I quite like vmware, but it's not always the best choice for all circumstances, or all users. If you'd also bothered to read my various posts, you would have seen that Windows 7 x64 was going to be my primary o/s. XP was there for a rainy day. The Debian install was there to do things that Windows doesn't natively support. And sometimes, I just like to boot into Debian! I could (and do) do lots of Debian stuff from a vm, and my current PC which is being problematic (hence my PC upgrade) has vms of debian, solaris, freebsd on it. If it's something quick, I'll fire up vmplayer. If it's more of an enjoyment thing, I'll boot into Debian proper. I've long had multi boot operating systems (harking back to the late 90s and lilo). I guess I'm a bit old fashioned in that respect. To each their own. And I think you misunderstood me re: piracy. I am firmly against piracy. I pay for all of my software, including some very expensive software. I also buy all my DVDs, Blu rays and music. Sadly, many of today's youth (and even older people) believe pirating software, music & movies is a right. And yes, I firmly understand that that damages the software company and the economy. That said, much software is vastly overpriced imho. Many software companies are plain greedy. Many who have replied to this thread have misinterpreted my intentions with XP. I have simple goals, and want to achieve them to have the system in the way that I envisage it. Implying that I'm deluded is not going to endear me! I have reasons for the way that I want to deploy this system, and I asked a simple question to bounce some ideas off what I was thinking. That didn't really require a lecture on not using XP x32 bit. All good, I'm pretty thick skinned and I know most of you mean well by your comments on XP 32 bit. I'm a bit hampered by not having played with recent hardware developments and I haven't really made a real effort to investigate them in depth like I would have done years ago. That's my fault really. And I didn't read the manual for the motherboard bios in its entirety - that's my stupidity and I deserve egg on my face for that. I'm getting on a bit and older people don't always learn new things quickly, or very well, and we don't always like change ;-) so humour this old fuddy duddy a bit ;-) peace Dave is all well and good.Don't use their products. Can I come use your lawnmower? Not pay to borrow it? Damage it? and expect you to repair it, and not care if I did it in the first place? I'm no fan of 'big business' either. But there is a limit. Little joey down the road pirating Windows is a moral 'meh' to me personally, he can do what he wants. However when a decision makes or breaks a company, and thousands of other companies that depend on them, I can respect their decision. Patching old shit isnt always the best. Otherwise we'd all be driving around in Model T's with 'Type R' badges, spinner rims, One recaro seat, and a supercharger on the original low compression motor. What? Patching is always the solution right? ps. you're right, the tone in this thread is quite negative and acidic, but thats because while we're offering solid reasons for microsofts practices, you refuse to compromise on your stance. Its frustrating, is all. Why ask, if you already know? Why try to teach, if you know its going to be against the norm? Just an observation.
  12. So how much did you pay for photoshop? Just under $700 for a full windows retail version. Dave
  13. I didn't make myself very clear in my original post (my bad, it was late!). My goal is a triple boot system - Windows 7 x64 ultimate will be the main day to day system. Debian will be there for mucking around with things or doing stuff that I can't easily do from Windows. XP will be solely a redundant drive o/s etc, it will not be used for day to day purposes. It's there for a rainy day. All my day to day work will be done in Windows 7 (including Photoshop). Obviously it'll natively see the SSD and ram etc and make full use of it. I'm well aware of the ram limitations on a 32 bit system. :-) I'm pretty confident that I've figured out the bios problem (being able to change the dram timing) and will test tonight. I'm pretty sure I've figured out why I can't install XP and why Debian is freezing part way through the install. Progress is being made thanks to some good suggestions from yourselves and me thinking and rtfm ;-) Dave And Photoshop CS6 is going to fly on your XP system that can only access around 3.4Gb of that 32Gb you've got installed. All that extra RAM you have in the system is made redundant because of the 32bit OS. You won't be able to access it. If you see people using 32 or 64Gb of RAM they'd be running a 64bit OS so they can actually use all of the RAM... Seriously you've just thrown money away buying so much RAM and sticking to 32bit. But hey in the end it's your money and your computer. Large organisations use products generally until end of support life and then will upgrade. This is why XP is still so 'popular'
  14. So how would you like MS to make money?They either stop supporting old software or you start paying a subscription. Which do you prefer? I find it funny how you say pc component quality has dropped, forgotten the early 2000's already? They only big failure I can remember recently were those dodgy Nvidia chipsets, "bumpgate"... ------------------------------------------------------------------------------------------------------ Back on topic: One error in memtest is too many. Take them back and get them swapped, this will probably solve the issues you are having. I don't really give a rats ass about Microsoft. Nor any other big business for that matter. As to hardware issues, well, all I can say, from my personal experience in 15 years of building my own computers, I've never had so many issues with a new PC. Every single other PC I've built has worked out of the box after the hardware install has been finished. Experience has also taught me that QC in general (not just in computers) is very poor these days. QC is generally the first thing that manufacturers cut when trying to increase profits from product pricing drops. Just my personal experience. ymmv. Dave I'm a photographer - Photoshop CS6 will sure like lots of ram! Especially with DSLRs with large image sizes. I see quite a number of other members on these forums going for 32 or even 64gb of ram! I guess we're all wrong ;-) Yes, I could set the motherboard bios to ide sata and try XP again, or I could leave it at ahci and load the ahci drivers for the motherboard via F6 at Windows install. I'll probably go the latter. As to the RAM, there shouldn't be ANY errors with the ram. Lots of places tell you this and it's quite elementary. it wouldn't be difficult for Microsoft to backport support for newer hardware, especially when XP is still the dominant operating system in the world. Or do you plan to tell me that Vista, Windows 7 and Windows 8 are all more popular? Microsoft doesn't do it because it wants to peddle Windows 7 and 8. As to profit, Microsoft has made a killing over the years, it wouldn't hurt them to lose a few dollars properly supporting a system, would it? Oh wait, the shareholders and profit are more important than your actual customers! I guess that's why people are leaving Microsoft in droves and going to Apple's OS X. :P As to Debian, if you'd bothered to read my earlier posts, you'd see it was a stop gap install to see what would happen. I know Etch is old. I was probably using Linux when you were still in nappies son. and I wouldn't piss on Redhat if you paid me ;-) I'm a Debian guy. Dave OK - weirdness ensues. Tried to load the custom ram timings in the bios (default F1 bios on the motherboard) - I can't edit none of the changes. Have re-read the manual several times, enabling 'quick' or 'expert' in the dram timing should let me make changes. But, it doesn't. Upgraded bios to F4s beta, still no go. Weird. Emailing Gigabyte to see what they think. with the 2013 I'm having so far, wouldn't surprise me if the motherboard is stuffed too. Only I could be unlucky enough to get a faulty motherboard and ram. I've loaded the xmp profile and testing ram now. Will see how it goes overnight in the morning. Also had a really good look at the qualified ram for this board - of the 8GB sticks, half of the memory sticks recommended as qualified are discontinued it seems. None of them seem available in Australia, except for the Kingston ram, which everyone is out of stock of, and it also appears to have been discontinued according to a few sites. Gigabyte should be updating the qualified ram if the list is like a year old (which is what it seems), but alas, why do that when you can peddle customers into buying a newer motherboard! Ah, I'm getting cynical in my old age. Dave
  15. Lucky i was referring to the maximum speed not minimum :) :-) Dave
  16. yeah, XP on the 120gb SSD alongside Debian Squeeze. I typically run VMs of Debian, Solaris and freeBSD from my main Windows install anyway. XP/Debian on their own physical disk are just redundancies. For a rainy day so to speak. I'm not worried about performance issues on them, that's not their raison d'etre. :-) re: speed limit, you are not legally required to do 60kph in a 60kph zone. It's drive according to the conditions. Yes, if you do 10kph in a 60kph zone, police can arrest you for being a nuisance on the roads (and rightly so I might add). But doing 50 in a 60 zone in pouring rain with limited visibility won't get you into trouble either ;-) Yeah, I'll rma the ram, but want to do more testing first to provide an accurate fault to the reseller. Dave
  17. Nah, not running XP 64 bit, that was a pretty horrid attempt by Microsoft (very poor driver support). Another half assed effort by Microsoft! Yes, the new system has 32gb of ram. Yes, XP is 32 bit. And yes, it'll only see 4gb or thereabouts. It doesn't mean you can't run XP on such a system, it just means you won't see the full benefit of the underlying hardware. XP would only be a fall back system, not intended for daily usage. My reasoning: experience has taught me that it's better to have a physical o/s to boot into than a vm. What happens if Windows 7 dies? That vm on windows 7 is as useless as tits on a bull to me. Don't they teach kids redundancy these days? Sorry for the snide remark, but it ires me that people are quick to jump to conclusion and then ram their discrimination's down my throat. I have my reasons for wanting to run XP. There's no reason why it shouldn't work (driver issues aside of course). I mean, the speed limit on most roads is 60kph, but it doesn't mean I must do 60kph! Rules aren't set in concrete. Anyway, thank you everyone for your suggestions. I'm not particularly au fait with the latest and greatest technologies, hence my post. I'm not dumb when it comes to computers either, just a bit rusty with the newer stuff and wanted to bounce some ideas compared to what I was thinking. I'll post my findings down the track - due to a busy life, I can't necessarily drop everything to test the new PC non stop and provide fast answers. I'll test over the coming days (will re-test ram with xmp and timing settings as per Corsair, then test each module singularly, then isolate the hard drives/optical discs). Given the errors in the ram though, I won't be keeping it. Dave
  18. Seriously? XP is the most used operating system in the world. It's numbers vastly outweigh Windows Vista, Windows 7 and Windows 8 combined. It's outdated? It's outdated because Microsoft fails to support their software, deliberately, to make sure that their newer software sells. It's a typical tactic of proprietary software. Gee could some of you guys have a more condescending tone? No wonder computer people aren't people people. Dave
  19. Updates are updates. Proprietary software companies love doing as little as they can, for as much money as they can. Sorry, I'm not a fan of proprietary software and never will be. memory test seems quicker this time - it's already at 93% this morning - yesterday it was like at 47% in the same time period, what gives? Just under 800 errors so far, over the 32GB. All on test 6, inversion (32 bit). And I highly doubt Corsair have sold 10s of thousands of these sticks. Most people probably never run memtest on the units, so probably don't know there's problems. The memory is sold as a kit, so I doubt that I can return just one stick (if it's problematic). Anyway, I'd rather return it and get different ram to be honest. No errors should occur during memtest, let alone 800 odd. Interestingly, yesterday, they were errors on test 6, today they are errors on test 8. Doesn't breed confidence. I'll let the ram continue running for a 2nd pass today whilst I'm at work, and then pull it out and return it to Umart tomorrow. We'll see if they honour returns. If not, onto fair trading. Debian Squeeze netinstall failed - well, it hung, installing procps (installing base system). Couldn't see any errors in dmesg, it just hung. Frustrating. There's nothing like spending 2k on parts and getting a lemon. I've never had such a p.o.s in all my years. But, experience has taught me that QC has all but disappeared in modern products. When you keep cutting costs, something has to give. I'll have a mate come around to check my build, just to make sure that I haven't done anything idiotic or missed something. I don't have time this morning to muck with xpm and ram timings, might do that tonight actually in hindsight. Still, memory shouldn't be failing, either in normal mode or xpm. I didn't bother attempting to install Windows 7 last night - if Debian Squeeze is freezing, then there's definitely problems and Windows has no hope in hell of installing imho. This all sums up 2013 so far for me...been a shit start to the year and just seems to be getting worse :/ (main PC is failing after 6 years with intermittent issues, macbook pro dead...). *sigh* Dave
  20. mmmm, am I doing something wrong? I started it last night as I said, it wasn't even 50% through the test (that's after 8 hours of it running). Unless it finished and was looping multiple times on me? Anyway, tonight, I get home, we had a blackout at around 11am, which has killed the test results. I'm just about to try a Debian 6 net install CD to see what happens. And then will pop in the memtest CD again and run it again. Dave
  21. melkor

    michael.jenkin Photos

    There's a wealth of information on the Internet!!! But I also have a lot of books in Australian spiders, including long out of print stuff. :-) Plus, there's not much I haven't seen in 10+ years of macro shooting. Dave
  22. I have some legacy stuff that I would prefer to run natively inside XP, and not in a VM. And there's nothing wrong with XP. I have a valid licence, I might as well use it! Yeah, I'll re-test memory with xmp enabled in bios and timing changed to what Corsair recommends in their troubleshooting. I'm pretty sure that Corsair has a major problem with this RAM module to be honest. Too many people are having issues. Disappointing that Corsair won't admit it and do a recall, but I guess big companies don't like to do that (makes them look bad). I'll also check the mb firmware and update that (probably the first thing to try). How long should it take memtest86+ to check 32GB ram? I started it at 11pm last night and it was still going this morning at 7.45am and not even half way through (unless it loops - but I couldn't see anywhere where it said loop # etc). I'll then try installing Windows 7 to the Samsung 256gb drive and see what that does and if it errors. I've got a growing feeling that it's a number of things - probably SSD not being seen by XP and Debian Etch, and also a RAM issue, all of them rearing their ugly heads. To be honest, it's why I hate proprietary software - Microsoft says it's supporting XP to April 8, 2014 (http://windows.microsoft.com/en-AU/windows/end-support-help), but doesn't provide updates to support newer hardware. But the software industry has a perpetual get out of jail free card when it comes to consumer rights it seems. Dave
  23. I wonder if the issues are because XP won't see the SSD (I haven't tried the F6 option to load raid drivers). I feel a bit lost here, cos this is the first PC I've ever built with a floppy drive lol. I've never used a usb stick to load drivers before and I hate new things. Perhaps I might try that. Also, I should be able to just load the Samsung disc in the other ODD and F6 during XP install and select the other ODD, correct? I'm not sure if USB devices are turned on in the bios by default or not. I'm also wondering if that's why Etch is failing. Might grab a Debian 6 netinstall disc tomorrow night and test that. Dave Yeah, I can do that as well, just a p.i.t.a, reminds me of mac os9 and extensions troubleshooting. Dave Just another update, RAM is failing on memtest86+ - exactly the same part of the test (test #6 inversion) as what tonnes of other people are reporting. I really believe that Corsair has a huge bunch of faulty ram on their hands. Will load XMP profile tomorrow and re-test and see if the errors come up, as well as do some of the troubleshooting that Corsair staff have mentioned on their forums to others. I expect it will make absolutely no difference. I've seen at least 2 threads on Corsair's forums, a bunch of negative reviews on Amazon, and a few on newegg's site. I firmly believe that Corsair should be recalling this RAM. I'll be returning it to Umart as faulty and unfit for purposes and seeing what other RAM is available (I want a 4 x 8GB kit, or at least if not in kit form, then the equivalent). Dave
  24. Bought one of these for my 2 Samsung SSDs for the new PC - what a useless piece of junk. Mounting holes do not match up with the drives, so cannot obviously mount my 2 SSDs. Not impressed. Basically has killed my PC building for the weekend. Unit will be returned to Umart as being unfit for purpose. Dave
  25. Well, an update and I feel like such an idiot. I had another guy at it tonight and turned the SSD over (so label side up) and viola, holes match perfectly. *egg on my face*. I have no idea why I didn't think to try this yesterday, perhaps just frustrating. This Brissie heat is killing me. But to clarify, the Silverstone SST-SDP08 perfectly fits the Samsung SSDs. Just idiocy on my part. Of course, the fun is that I don't have a magnetic screwdriver (duh, didn't think about getting one of those today duh!). I'll persevere and get the 2nd SSD in!!! Thanks to all that replied. Dave
×