Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Fusion crashes an the nod can not be opened

  1. #11
    Franklyn
    Guest

    Default Re: Fusion crashes an the nod can not be opened

    Backup 101:

    Exporting your site to template is a good thing, It is NoF's version of
    Backing up your site however you must do this manually as there is no prompt
    for you to do this as you'd get from say, quickbooks or some other program
    that has a database. NoF makes backups of the .NOD file which should keep
    you from loosing to much data. I'd recommend frequent saves of your site as
    you develop (ctl+s) and if you do get a crash you may only loose a few
    minutes work. After any major revision you should export to template this
    way if you do have a major crash and you cannot recover from the backup of
    the .NOD file you still have your site and can be up and running again
    within 1 min and what ever changes you need to make / add.

    Franklyn.


    "Nancy O" <nancyoshea1@NOSPAMverizon.net> wrote in message
    news:ekfbfp$8np16@flsun90netnews01.netobjects.com. ..
    > If you Export site to Template, you get a zip file of the nod (database),
    > styles and assets used in your site.
    >
    > When catastrophe strikes, a user can generally create a new site in NOF
    > based on their template zip in about 60 seconds. Problem is most new
    > users
    > don't see the need for templates until it's too late. I think NOF should
    > prompt users to Export Sites to Templates every time a nod file is closed
    > (with an option to turn off the alert in site settings, of course).
    >
    > --Nancy
    >
    >
    > <sandy@byuk.co.uk> wrote in message
    > news:MPG.1fd52aec60a2caa99896a0@news.netobjects.co m...
    >> In article <ekdf0k$1ej4@flsun90netnews01.netobjects.com>, gary@gwd.net
    >> says...
    >> > Hi Sandy,
    >> >
    >> > Like Chuck said it is a database.
    >> >
    >> > The database is made up of one file, it is not a collection of files

    > that
    >> > you would zip.
    >> >
    >> > This one file has pointers to file locations, etc. but does not include

    > the
    >> > files.
    >> >
    >> > .nod is the extension to the proprietary database format of NOF.
    >> >
    >> > Hope this helps in your understanding on how NOF handles files and the
    >> > database structure.
    >> >
    >> > Gary
    >> >

    >>
    >> Nonsense.
    >>
    >> .nod doesn't contain files?
    >>
    >> Ok so write the file as plain text and zip it.
    >> There is no excuse for not doing so.
    >> Its the simple approach, its the most recoverable approach, it's the most
    >> sensible approach.
    >>
    >> .nod has repeatedly lost masses of data for many people. I've seen it
    >> here frequently & god only knows a newsgroup is always the tip of any
    >> iceberg.
    >>
    >> Continued use of .nod files should be untenable to everyone.
    >>
    >> sandy

    >
    >




  2. #12
    Boris
    Guest

    Default Re: Fusion crashes an the nod can not be opened

    Hello Mike,

    Did you solve your problem yet? I had the same thing happen to me lately. Thank heavens for the versioning. I download the last version into the /Template directory, renamed the current directory where all the website info is (for the NOD you are having problem with) and started a new session of NOF. When it starts I just select the template and give it the same name as the one I had the problem with. I then copy in any assests that I might want to have included.

    It seems that the ZIP files in the versioning are just like templates (probably actually are), so I was covered that way.

    Hope it helps,

    Boris
    "Michael Menard" <Michael.Menard@uni-klu.ac.at> wrote in message news:ek1j8n$j4810@flsun90netnews01.netobjects.com. ..
    Hi!

    I use versioning with npower ot with fusion.

    Sometimes fusion crahes when exiting. so from that point on

    1. Fusion crashes with the project and can not be opend again
    2. Npower crashes
    3. all backups are crashing !!!!!!!!
    +#@€

    HEEEELP

  3. #13

    Default

    Contrary to what might be inferred from the responses above, this problem isn’t limited to opening older files in a newer version of NOF.

    I had this happen to me with a file created in NOF v. 11 after the program crashed. When I re-started the program and open the file, got this message:

    Runtime Error!

    Program: [file location]

    This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
    Trying to open it again, before shutting itself down NOF unhelpfully kicked in with the following error message:

    This file contains an instability. If this file was created in an older version of NetObjects Fusion, it is likely that the instability was introduced by that version. Please use recover.txt, located in your /NetObjects Fusion folder, to lean an alternative method of opening this file.
    As previously mentioned, there is no “recover.txt” in the NOF folder.

    I’d sure like to know what the “alternative method” of opening a file damaged in this way is. Not only has this problem (whatever it is) made my working file unusable, but has also similarly wrecked the most recent ones in the Recovery folder.

    Very, VERY frustrating.

Posting Permissions

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