Results 1 to 2 of 2

Thread: N5200Pro no shutdown after IMGDUP install

  1. #1
    Registered User
    Join Date
    May 2008
    Posts
    3
    Thanks
    0
    Thanked
    0 times in 0 posts

    N5200Pro no shutdown after IMGDUP install

    hey all

    i love my all new n5200pro fw (2.00.04) - what a nice toy.

    after the install of the IMGDUP module to add some eyecandy to the webui, i run in some problems to shutdown the n5200pro. i can't shutdown the n5200pro by the power mng tool anymore.
    when i want to shutdown manually i have to shutdown the machine twice...!
    it seems like the first shutdown kills the IMGDUP module and the second shuts the machine down...?!

    does anyone have a fix for this...?

    thanx

    Diamondback

  2. #2
    Registered User
    Join Date
    May 2008
    Posts
    3
    Thanks
    0
    Thanked
    0 times in 0 posts

    Re: N5200Pro no shutdown after IMGDUP install

    hm, that doesn't look to good now does it?

    h**p://thecususergroup.proboards106.com/index.cgi?action=display&board=n5200modifications&thread=1656&page=1#8798

    last post:

    Tairus,

    although it would be technically not too difficult, I personally don't like this option too much....

    I'm not keen on creating new "own" versions of the firmware every time Thecus issues an update.

    Thecus did honour some of our "improvements" and added them to the official releases and I assume they will behave the same in the future.

    The only pity is that Thecus definitely has no real experienced programmers - just have a look at the Shell scripts - most of them look horrible and they are on a beginners level.

    As for additional kernel modules, we are currently not dependent on having the system in flash memory because of the modules being able to be loaded from any place.

    My IMGDUP module still has the disadvantage disturbing the shutdown sequence. I've tried to prevent this in my SHUTDOWN module but it is still not enough.

    But I don't want to be too destructive: we could create another partition on the flash drive and then copy everything below /img to that partition. Then we just need to modify the startup script which gets called on bootup not to use the cloop images but to use that partition.
    When a new firmware gets released we just need to copy /img to that partition and everything should be up to date.

    Just my 2 cents.....

    Andreas

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Clean install of XP - what apps to install?
    By cotswoldcs in forum Software
    Replies: 27
    Last Post: 19-04-2008, 05:27 PM
  2. Quicktime install Failure-Deploy MSI needed pls!!
    By hegaroo in forum Help! Quick Relief From Tech Headaches
    Replies: 2
    Last Post: 13-11-2005, 06:53 PM
  3. Possible MMC 9.06/9.08 to T550P MOD
    By Octavean in forum Graphics Cards
    Replies: 2
    Last Post: 11-08-2005, 03:59 PM
  4. Bios & install guide for Epox 8RDA+ (probably other nforce2 MB's too)
    By Ravens Nest in forum PC Hardware and Components
    Replies: 10
    Last Post: 25-08-2003, 02:03 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •