• Content Count

  • Joined

  • Last visited

  • Days Won


gericb last won the day on August 3

gericb had the most liked content!

Community Reputation

10 Good

About gericb

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. WELCOME BACK @FOXBI !!! You are most welcome!!! I hope all is well with you. I will look forward to your renewed creative magic. ๐Ÿ˜Ž
  2. I suspect that the overwhelming replies, feedback and aggressiveness of some here, might have alienated poor @foxbi, where he felt it was no longer worth the stress and effort in his daily busy working/personal life to devote anymore attention to his great work and efforts. If I am not mistaken, I believe along the threads, he has provided the source code and GitHub, other creative information/tips on how he made this magic for us....someone else might want to consider picking up where he's left off, back in December 2018.
  3. Would it be possible for you to contain in your program the โ€original" DSM Syno JavaScript File / Data. This way would could just select option #3, and always have the ability to overwrite any changes that have been made, back to factory defaults, and not rely on a โ€œbackupโ€ to be restored? ๊ทธ๊ฒƒ์€ ๋‹น์‹ ์ด ๋‹น์‹ ์˜ ํ”„๋กœ๊ทธ๋žจ์— "์›๋ž˜" DSM syno ์ž๋ฐ” ์Šคํฌ๋ฆฝํŠธ ํŒŒ์ผ/๋ฐ์ดํ„ฐ๋ฅผ ํฌํ•จ ํ•˜๋Š” ๊ฒƒ์ด ๊ฐ€๋Šฅํ•  ๊ฒƒ ์ด๋‹ค. ์ด๋ ‡๊ฒŒ ํ•˜๋ฉด ์˜ต์…˜ #3๋ฅผ ์„ ํƒ ํ•˜ ๊ณ  ํ•ญ์ƒ ๋ณ€๊ฒฝ ๋œ ๋‚ด์šฉ์„ ๋‹ค์‹œ ์ถœํ•˜ ์‹œ ๊ธฐ๋ณธ๊ฐ’์œผ๋กœ ๋˜๋Œ๋ฆด ์ˆ˜ ์žˆ์œผ๋ฉฐ ๋ณต์› ํ•  "๋ฐฑ์—…"์— ์˜์กด ํ•˜์ง€ ์•Š๋Š” ๊ฒƒ์ด ์ข‹์Šต๋‹ˆ๋‹ค.
  4. OK. Seems logical to me, if you could include the functionality to simple restore the "original" DSM code/information in those cases where things might have become corrupted or the backup was no longer the "original" DSM code/information. Something quite and simple. What do you think? Thank You for all of your hard work and magical code work! MUCH APPRECIATED!
  5. Curious...have you by chance, included in your code, the "original" DSM Model Name, CPU, CPU Clock Rate, CPU Cores in your code, for the "3) Restore" function, so that it's possible to overwrite flawed data with the factory original version?
  6. Hehehe, but that is an old tech cop-out for not keeping things updated as they should be. In my line of work, IT Mgr at a major hardware manufacturer, they use to following this notion but then wondered why there was always some kind of compatibility issue, security flaw, performance issues, etc., etc. Respectfully, clinging to vintage software from the past, just because, isn't really forward thinking and productive, if there are better options...if not, then of course. Only this policy was changed, proven metrics of increased system reliability, but keeping things up to date. There is no reason that anyone should have issues using something newer, it is literally point and click. They are still working on "bug fixes" for making Windows 7 USB, ROTFL! Rufus can smoothly be used for Windows 7-10, Ubuntu, DSM, Linux, macOS, Windows Server, as I can personally attest. I know it's only a simple USB tool, but the overall point is still valid I think. ๐Ÿค“
  7. Certainly I am not a GURU with all the configuration nuances with this project, but definitely loving it, I've had my stupid questions and little issues...that being said, Rufus is so straight forward and easy, if someone can't even figure out how to use that, probably shouldn't be here trying to go any further. In general, if a piece of software is never updated, even the most simple of them, it's time to move on, especially when there is something better and still being supported. ๐Ÿ˜œ
  8. Hey there Jensmander - LOVE your concise/aggregated tools. I would like to suggest a change though, to use Rufus USB Imaging Tool, I use it for everything of this type, including for DSM .img/.iso etc. it rocks AND it's updated regularly. The tool you have included is v1.0 and never been updated since. I have sent you the "portable version" as a PM, but you can find it infinitely better tool for such things, hands down! Thank You, Greg
  9. Thank you for your original work and willingness to continue to improve, based on feedback -- this is the most important thing. Your willingness to create and release for others to enjoy the enhancements, is very much appreciated. If you feel there are parts of your coding that you'd rather not be public, for personal reasons, I think that is fine....otherwise, being able to view "the magic" of your scripting, helps others understand and learn new things maybe. In the end, it's YOUR choice what you want to do. ๐Ÿ˜Ž
  10. Doh!!! I forgot to check this too...I can confirm the same findings/issue, using V5.0 on all 3 of my systems. It's showing the updated info correctly in SYSINFO/Control Panel, but "Original Info" when DS Finder & DSM Mobile. I am sure a quick fix for FOXBI will knock it out. ๐Ÿ•ต๐Ÿปโ€โ™‚๏ธ
  11. You just plugged the DOM into a PC, wrote the synoboot to it? Isn't it only 512MB in size? Did it support all the hardware str8 out of the main loader, or did you have to use the extra.lzma?
  12. SUCCESS! Correct # of cores being displayed, and I appreciate the extra CPU stats presented from the v5.0
  13. That's exactly what I was trying to share in my earlier post, if just based on the numbers alone....don't know if it's displaying based on Hyper-Threading capable. ๐Ÿค”
  14. FOXBI! You are TOTALLY making us happy, I have been wanting to change this CPU INFO forever, so you're hard work in finding where it is, and how to change it - IS WONDERFUL!!! if you search through the forum, you will see many people regularly say that it "could not be changed, as it was hard coded..." and you have clearly proved these statements to be totally uneducated and wrong. I appreciate your work, you are in no way rude or need any forgiveness, you are making great things happen!! ๐Ÿ˜Ž Just trying to help you as best I can, I APPRECIATE you and your creativity/work.
  15. But it's wrong though. In Image #2, 4 it's showing 4 cores, which isn't correct as validated by Image #3 directly from the BIOS. This is a bare metal install, no VM, no HT option to enable/disable. The i3-4130 is the default CPU info from the DS3615xs, my system is the i3-3220 (BIOS image #3). But CORES and THREADS are different, not the same. Seems you are display for CORES, the what is actually the THREADS. As far as the CPU frequency goes, 3.29Ghz where is it getting that from, since it should be 3.30Ghz and none of the command line data or BIOS indicates that value. ๐Ÿค” Do I make sense? ๐Ÿค“