Re: [NTB] Back to Keeping my OPEN Files After A Reboot...
> However, to clarify this time (~Big Smile~) I'm using Windows 98 SECharles' idea about memory being the problem is valid, but in Win9x my
> (happily, by the by) and have full control over all aspects of my
> computer... (And a fair handle on how to use it, I guess.)
experience was always that running out of resources became an issue long
before memory (RAM) caused problems.
Just to make sure either or both is not was causing your problems - can you
confirm that you have Resource Meter (from the Win98 distro) and/or one of
TClockEx, ProcessMonitor, TaskInfo2003 (all freeware or light nags - just
Google) running to show whether it is a shortage of Resources causing your
It would be worth retrying what ever causes your failure symptoms under a
*very* light load. ie - close all other apps and make sure nothing not
required is being invoked at startup and see if you get the same or
Addressing two of your specific problems:
> I'm going to have to figure some way to recall where things are. IAs a workaround until the main problem gets solved - could you build a
> have subfolder upon subfolder I work with and files from literally
> dozens, so I can't say how confusing and annoying it is not to be
> able to have the essential files open when I need 'em.
Favorites list that includes all the files you want to be able to access and
use QuickList to select from for the file/files you want to work on?
SysTray icon for Notetab: When I was using Win98 I always had problems
getting this feature to work consistently too - others have reported similar
problems. Usually clicking the option off/on (OK'ing between each in
Options) seems to help but long term I found it more useful to just leave
Notetab on the taskbar.
This also allows you (if you want to open a file from Windows Explorer) to
drag the file(s) on to the TaskBar-Notetab button - wait a second or two -
Notetab window gets restored - drop it/them into Notetab. Note: I didn't
discover this till after switching to Win2K so I'm not posiitive it will
work in Win9x
Long term: Get Win2K or WinXP - the time you save in not having to reboot
never mind the other advantages will be so gooood :-)
Regards ... Alec
---- Original Message ----
From: "KevinR" <kevinroyal01@...>
Sent: Thursday, January 15, 2004 13:22
Subject: [gla: [NTB] Back to Keeping my OPEN Files After A Reboot...
From what you have described to date, here are some new solutions to try to fix your problem.
The first is a temporary fix that will get you by, and that is to put the files that you work with in one or more favorites categories and call them up as you need them from the Quick list pane.
This way you don't have to hand write that list. :-)
I don't know how you are launching NTP but if it is from a shortcut, I would look at the path in the properties of that shortcut and verify that you are opening the NotePro.exe that you think you are opening.
You can check it out too by double left clicking the NotePro.exe file in the C:\Program Files\NoteTab Pro folder to launch NTP.
You might also rename your C:\Program Files\NoteTab Pro directory to C:\Program Files\NoteTab Pro OLD rather than deleting it or installing over the old files and then reinstall NoteTab Pro such that it is forced to write to a different area on your hard drive. A bad block on your drive where the current NoteTab files are stored can cause all kinds of grief.
You are running Win 98 and as happy as you think you are with it, it is going to cause you nothing but grief with NoteTab or any other fully loaded editor if you are trying to load 30 files.
It is not necessarily a shortage of RAM that is the problem. It is a lack of resources available when using 98 that causes 99% of the problems users incur with NoteTab Pro or other heavy duty editors of it's class.
As well, if you are running a lot of TSR's or other utilities (AV or FW or IM or Memory managers or popup stoppers etc) in the background, they are all using resources that NTP wants/needs depending on how you have it configured and what you are doing.
The solution for you is to go to NT, 2K, or XP which gives you the same amount of resources for each individual window that you open as you now have for all of the windows you have open to share.
Then you can open windows until you run out of RAM.
I can tell you this but until you do it, you can't appreciate the significance of it.
At 10:22 AM 1/15/2004, you wrote:
First off, thanks to everyone who answered me first time 'round. It's
However, to clarify this time (~Big Smile~) I'm using Windows 98 SE
(happily, by the by) and have full control over all aspects of my
computer... (And a fair handle on how to use it, I guess.)
I tried what was suggested--both renaming and totally removing
the .ini file from my NoteTab Pro folder.
That worked fine through *one* reboot (shut off at night and booting
next morning) as I recall...
Hasn't worked probably 9 times out of 10, though.
In other words, I've done that over and over (and over again (the
renaming) to try and get it to 'stick.'
I have to say that it's very frustrating, as I often work with 20 to
30 open files that I'd like to 'find' next go 'round... (Lordy, I
even thought about starting to keep a handwritten list. But I'd
forget every single time...)
I'm going to have to figure some way to recall where things are. I
have subfolder upon subfolder I work with and files from literally
dozens, so I can't say how confusing and annoying it is not to be
able to have the essential files open when I need 'em.
- On 15 Jan 2004 at 18:22, KevinR wrote:
> Anyway, the defaulting to the systray cleared up, although theYou are really starting me to think that you are experiencing hard disk
> software *never* opens first time 'round. (I don't ever double-click
> the icon anymore, as that *never* seemed to open it properly--in case
> anybody here cares. I'd always right-click and select Open, as that
> worked better. But now that *never* works the first time I try it. It
> takes twice every time to open it... A sure sign my Open files will
> be gone, by the by...)
errors through fragmentation of actual physical errors. When was the last
time you did a scandisk and a defrag? It sounds like NT is trying to write
to the disk, but something isn't allowing it to do so consistently. Why
this is happenning to NTP and not the lite version may have more to do with
where on the disk the program files are being written to. Try the scandisk
and defrag first, then see if NTP starts saving your settings properly.
Thought for the day: If man does his best what else is there? George S.