Jump to content
XPEnology Community

billat29

Member
  • Posts

    351
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by billat29

  1. @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.
  2. 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.
  3. Luckily I still have the logs .... update.synology.com checkip.synology.com autoupdate.synology.com
  4. 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
  5. 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
  6. 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.
  7. 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.
  8. What hardware are you running? and what version of the bootloader are you using. I'm a bit worried about "system.img"
  9. billat29

    DSM 6.1.x Loader

    viewtopic.php?f=2&t=20216&start=1998
  10. billat29

    DSM 6.1.x Loader

    When jun originally posted 1.02a he said "no AMD yet"
  11. It's an alpha version. OK for testing but I wouldn't trust my data with it yet.
  12. billat29

    DSM 6.1.x Loader

    are you selecting the amd-boot option? Nope, should I ? Thanks! Yes. You should.
  13. billat29

    DSM 6.1.x Loader

    I would be surprised if you could see the files from WIndows Explorer. I used OSFMount to mount the image as per the tutorial referenced here http://xpenology.com/forum/viewtopic.php?f=2&t=20216
  14. Sorry if this is *** obvious and you have checked this - but is the VM trying to boot from the new disk rather than from the Xpenology boot loader?
  15. Does anyone read what I wrote above? READ. Happens every release I did once think of writing a general guide - read the forum; set auto updates off; don't update until you know it works; always have a backup; and above all - read the forum. But noone would read it
  16. Yes. The next screen should be the one that asks you whether you want to keep all your settings or not.
  17. The virtual disks are too small. Try 20Gb each - and you can choose not to allocate all the disk space when you create them
  18. Check that they are not both using the same mac address
  19. When you setup your DSM, did you go into Control Panel and change the update settings from "newest DSM and all updates"? If not, then I am going to guess that it downloaded DSM 6.0 and tried to apply it. So. What to do? You could read this http://xpenology.com/forum/viewtopic.php?f=2&t=13288 and try the suggestions there. Note the disclaimer
  20. It's been running on my N54L (disclaimer: There's a HP NC360T card in it) for at least 10 days. So far without me noticing any problems.
  21. Ah wait. Are you trying to install DSM5.2 with jun's loader? That won't work.
  22. I'm a bit confused about what you are doing, but then if you have been struggling with this for a while, then you have tried "everything". So. In your searches, have you found that your LSI card is supported? What version of the bootloader are you using and where did you source it? I just found the USB stick I was previously using for 5644.5 and I seem to have been running the unmodified cfg file. So you shouldn't need to modify anything.
  23. "Workstation Player supports physical disks up to 2 TB capacity." https://pubs.vmware.com/player-12-windo ... -guide.pdf page 142
  24. I was waiting for the much discussed quicknik release hoping for the same driver to get my USB printer working on my N54L, and then I found a USB 2.0 hub in my box of computer bits. I plugged it in (unpowered) and it all worked.
×
×
  • Create New...