billat29

Members
  • Content count

    107
  • Joined

  • Last visited

Community Reputation

0 Neutral

About billat29

  • Rank
    Advanced Member
  1. DSM 6.x.x Loader

    No, AMD CPU is not supported on the latest loader. (N54L comes with AMD CPU) Jun has stated there are issues with it and disabled the AMD support. You will have to wait until there is a new loader out with support. You can get to 6.0.2 Update 11 with the 1.01 loader (see http://xpenology.com/forum/viewtopic.php?f=2&t=22100) but that's as far as you can currently go. As bchuter says, AMD is not currently supported on the 1.02 loader. Maybe it will in future. Maybe it won't.
  2. How to add my entire hard drive

    Ok. So what have you been able to do? Before attempting to add a physical disk, you should have imported the virtual machine files from June loader. Did you do that already? EDIT: Oh yes and my assumption is that your 3TB disk has come out of a DSM bare metal installation and is not a random disk with data on it. EDIT AGAIN! Ah and then I remembered. Check the VMWare documentation. I recall that Workstation only allows physical disks up to 2TB.
  3. How to add my entire hard drive

    Create a new virtual machine using the wizard. You will have to create it with a virtual disk at this point. Save your new VM then go back and edit the virtual machine. Add a new HDD (choose a sensible type that matches your real disk) and then you will get the option to use a physical disk
  4. N54L Setup and working but a couple of questions

    Here are the release notes https://www.synology.com/en-us/releaseNote/DS3615xs so you can see what vulnerabilities are fixed in later releases and make your decision based on that.
  5. N54L Setup and working but a couple of questions

    Did you get the 4Gb working? I can confirm that DSM reported 6Gb on 5.2 on my machine. I installed a crucial 4Gb ECC module some time ago and it all just works. I can't comment on the firewall, What I can say is that later versions of the 5.2 loader disabled writing to the BIOS and that stopped power schedules from working but other than that my box worked fine on later versions of 5.2. Do check that you have the correct setting in update and restore - important updates retaining the current version of DSM or you will be trying to get V6 working with the V5 loader!
  6. Say bye to Quickconnect

    Wouldn't package updates or even DSM updates go via this? I would have thought blocking these would prevent DSM updating itself and you have to manually download and install from your PC. That may not be such a bad idea, given the number of people who post "My DSM updated itself and now it's broken". I think my point was that apart from the discussion around QC, DSM contacts synology.com for various reasons. It could supply your external IP, serial and mac and any other information it has if it wants.
  7. Say bye to Quickconnect

    I would be very happy at that price. I suspect at that level, there would be a risk of substantial cannibalisation of their hardware business but let's see what actually happens.
  8. Say bye to Quickconnect

    @fonix232 Interesting. There is a theoretical point about not putting more restrictive terms on GPL code but we're only be arguing about a small part of the system. What you say makes sense. Synology are not immune to the same market forces that have shaped the computer industry and that means first - you can only make money selling boxes for so long and then you need to unbundle the software and services. Second, when you do unbundle, if you go do the route of selling upfront software licences, then at some point you find you are not getting new users and you run out of reasons to sell new licences to your existing users. Hence Cloud and subscription based functionality. However, this will only work for them if the guys who made their reputation in the company by shifting boxes can change their mindset to the new order. My experience in the industry says that is not certain.
  9. Say bye to Quickconnect

    OK I'll bite. The fact that the Quickconnect code may be covered by the GPL does not give us the right to use any service that it connects to. We could use the code to define how to implement our own QC service and modify our version of the DSM code so that it points to ours not Synology's. But using theirs, indeed, creating false credentials in order to do so, could well fall under the scope of various computer misuse acts around the world.
  10. Say bye to Quickconnect

    Luckily I still have the logs .... update.synology.com checkip.synology.com autoupdate.synology.com
  11. Say bye to Quickconnect

    Just to add to the general paranoia : While I was testing a DNS server on my network (and looking at the logs), I found that my box - which has quickconnect off - contacted account.synology.com and another url (I forget) which retrieved my external IP. So they probably have a better idea of how many people are running XPEnology than anyone here
  12. Have you selected option 3 for AMD in the menu? Hang on. Are you using the v1.02a alpha loader? I don't think it has AMD support in it
  13. Can we change the forum rules?

    I was very pleased to see that Andy was back and doing an update. I had a bet with myself about how long it would be until someone asked when is it ready. I lost. It looks like a big change so I'm sure that migrating the existing content, users etc will not be a trivial task - especially as most existing installations have probably taken each upgrade step along the way. But I'm looking forward to it.
  14. Can anyone suggest any help or places where the confirmed latest build of Jun's loader can be downloaed please? It works on N54L. My signature shows that I have an additional nic (left over from another project) but I can confirm that the onboard nic works just fine. I followed the procedure in the first post of this thread. If you read it, it will point you to jun's OP. Right at the beginning of jun's post are two links either of which will get you the right loader for 6.0. Be aware that the first link gets you to a folder which also contains jun's alpha loader for 6.1. You don't want that one. You want v1.01.
  15. What hardware are you running? and what version of the bootloader are you using. I'm a bit worried about "system.img"