Conference terri::tdl

    I've tried to reproduce this (Mark and I have exchanged mail on it) and
    I can't. I've tried a 486/DX2-66 here at work, and my 386/40 at home.
    Both are running DOS6 and Windows 3.1, scratch installations both
    times. No problems at all, except on the 486 when it was so fast I
    almost missed it!
    
    Laurie.

    
    I tried again last night, but no joy.
    
    I even tried putting F:\TDL in my path, but it still spits out "Not a 
    Valid Path" whatever I enter.
    
    I'm very puzzled. I've never had any problems installing software, but
    I can't get anywhere with this.
    
    Very odd.
    
    Mark

    Mark,
    
    I've just tried all manner of variations on a PC here, 486/DX2-66
    without a problem. I've tried from floppy, from a c:\ dir, from an
    SUBST'd drive, with a trailing \, and without. You name it, I've tried
    it. No problem. All I can suggest is, if all else fails, install it
    manually. Let me know, and I'll get a list of what goes where for you.
    
    Laurie.

    One thought Mark, the ZIP you have is clean isn't it? No transfer
    problems?
    
    Laurie.

    
    No it came over fine and it's unzipped with no problem.
    
    How would I go about installing it manually?
    
    Mark

    I'll get you some instructions.
    
    Laurie.

    I notice one difference between what the two of you are saying... one's
    on C: and one's on F:   Is F: a network drive?  Some special disk? 
    Have you checked LASTDRIVE in config.sys?

    RE: .-1
    
    I think that Mark's trying to install it on a stand-alone PC, so it's a
    good point, but not relevant here, I suspect.
    
    Ok, Mark,
    
    Unpack the ZIP file to (say) a:
    Then this is where the files have to go (in say, c:\tdl):

    a:\tdl.exe     c:\tdl\tdl.exe
    a:\notepad.tdl c:\tdl\notepad.tdl
    a:\winword.tdl c:\tdl\winword.tdl
    a:\write.tdl   c:\tdl\write.tdl
    a:\readme.txt  c:\tdl\readme.txt
    
    a:\declist.rto  c:\windows\system\declist.vbx
               ^^^                           ^^^
    *** note filename change..................^
    
    a:\infovbx.vbx  c:\windows\system\infovbx.vbx
    a:\vbrun300.dll c:\windows\system\vbrun300.dll
    a:\cmdialog.vbx c:\windows\system\cmdialog.vbx
    a:\commdlg.dll  c:\windows\system\commdlg.dll


    Then you need to provide a skeletal TDL.INI in \WINDOWS that looks like
    this:

    [Setup]
    FileLoc=C:\data\TDL\
    ExeFileLoc=C:\exe\TDL\

    Where, of course, the correct EXE and DATA dirs are given. Do put
    in the trailing backslash. Normally, all this is done by the install
    proggy.

    Let us know how you get on.
    
    Cheers, Laurie.

    
    Cheers Laurie,
    
    I've got it installed. Now to try it out.
    
    Mark

    Hi!  I was the noter on "shareware" who couldn't get TDL to install on
    my PC.  Thanks for your instructions; it is now up and running.  
    
    However, I must say that I also tried every trick to install and kept
    getting drive ":\" didn't have enough space.  I also tried to install
    from a: to b: and that failed as well.  I have a 386 pc.  
    
    Well anyway, that is behind me know!  I've got the postcard in the
    mail!
    
    Regards,
          
    
    Rhonda

    
    Having got TDL installed and seemingly running, I decided to add a note 
    to one of my items.
    
    Result : Not a Valid Path...
    
    I'm using NOTEPAD. I checked the TDL.INI, but couldn't see anything
    specifically related to the note taker, so anyone else had this or know
    what needs changing? 
    
    Obviously, I didn't do a REAL install, so maybe there's a step missed 
    somewhere?
    
    Mark

    I'll install it here and see what's what. But briefly, have you checked
    everything is set up correctly in preferences?
    
    Laurie.

    Mark,
    
    Here's a TDL.INI file from a "virgin" installation. In other words,
    before any preferences have been applied.
    
    [Setup]
    FileLoc=c:\tdl\
    ExeFileLoc=c:\tdl\
    
    Assuming your preferences are correct, I'm beginning to wonder if the
    problem with invalid path is perhaps something to do with your path
    statement in AUTOEXEC.BAT, and the entry for Windows is corrupt. Is
    your path <= 128 bytes long? Have you got a ; hanging on the end of the
    path statement? Are you sure the path is "clean"?
    
    The reason I say this is, that NOTEPAD etc. are external to TDL, and
    called therefrom, through Windows. As you had this problem (same error
    message) installing TDL, I think there's something funny with your set
    up somewhere. How do you fancy another install, but this time start
    Windows with a /B switch, and post the log file of the errors.
    
    Laurie$grasping_at_straws.

    
    Ok, I'll go away and try looking at my PATH, etc.
    
    If I get nowhere, I'll post the results of a WINDOWS/B installation here.
    
    Cheers for now.
    
    Mark

    
    Ok.
    
    I checked the PATH and there was a buglet in it (no colon after a
    drive letter), but that made no difference.
    
    I did a WINDOWS/B and there are no errors in the log.
    
    However, I did find out that the error only occurs if I select an item
    prior to starting up notepad (or write). If I have no item selected,
    the Notepad or Write (I don't have Word) programs start up fine.
    
    Still baffled.
    
    Mark

    I've sent a mail to Keith, we'll discuss the problem. I wonder if it's
    because you don't have Word... I've never tried to install to a machine
    without it. Until the SETUP code arrives, I can't check, but it might
    just assume Word is installed. I know Keith uses it.
    
    Laurie.

    What is drive F: Mark?

    
    It's a stacker drive on Drive D:.
    
    Could this be the problem? Nothing else I've installed has trouble with 
    Stacker, though.
    
    Mark

    Ok Mark,
    
    I've spoken to Keith, and it seems it's like this;
    
    TDL uses the TDL.INI file to find Word or Write. The section it uses is
    this one:
    
    [Setup]
    FileLoc=C:\data\TDL\
    ExeFileLoc=C:\data\TDL\

    Note, NO spaces, *MUST* have trailing "\". I know I mentioned that
    before, but it's something you need to check. If that's all ok, then
    there's a possibility that TDL is (for some reason) not seeing your
    TDL.INI file. Do a "save" from the file menu, which -  amongst other
    things - will save the location of the main screen in the  TDL.INI
    file. Then look at the \Windows\TDL.INI file and see if it has more in
    it than you put manually. If not, search every disk for another one:

		C:\> dir/s C:\tdl.ini
		C:\> dir/s D:\tdl.ini 
		etc

    Is there another one somewhere? If so, adding the fileloc stuff (see
    above) should  fix it, but please tell me if there is, Keith needs to
    know if/why the .INI file is appearing somewhere else.

    Cheers, Laurie.

    
    How does TDL use those lines to find Write?
    
    Write isn't in the same directory as TDL... 
    
    
    Anyway, I've only got one TDL.INI (in C:\WINDOWS), it contains the 
    following :-
    
    [Setup]
    
    FileLoc=F:\TDL\
    
    ExeFileLoc=F:\TDL\
    
    
    
    [General]
    
    Left=0
    
    Top=0
    
    Width=7905
    
    Height=4860
    
    Note=Notepad
    
    DeleteNote=0
    
    LapTop=0
    
    DblClick=4
    
    DefaultDisplay=7
    
    ConfirmDelete=8
    
    SortOrderPD=0
    
    
    
    [Colours]
    
    High=255
    
    Medium=12582912
    
    Low=0
    
    Overdue=255
    
    Normal=0
    
    
    
    [Databases]
    
    Name1=
    
    DB1=f:\tdl\tdldata.dat
    
    Default=1
    
    Hope this helps.
    
    Mark

    Thanks Mark.
    
    Where is WRITE.EXE then? It whould be in c:\windows
    
    I'll talk to Keith again.
    
    Cheers, Laurie.

    
    Yep, it's in C:\Windows, but those lines in TDL.INI point to F:\TDL...
    
    Funny how it works when I don't select a note first, isn't it?
    
    Maybe there's a problem with the manual installation procedure
    mentioned earlier (I'll check all the files are where they're supposed
    to be.).
    
    Mark

    Mark, the TDL.INI stuff is only relevant to TDL. It looks in the
    default place for things like WRITE.
    
    Try as I might, I can't reproduce this!
    
    Laurie.

    
    Found the problem.
    
    DOS 6.0 had modified my AUTOEXEC.BAT to LOADHIGH APPEND. This made the
    line too long and left a hanging append. Removing the rogue F:\T from
    the end solved the problem with notepad. I now have items with notes
    attached.
    
    Tell Keith a postcard will shortly be on the way! 
    
    Mark

    Brilliant!
    
    Keith will be pleased. If he'd got any hair left, he'd be tearing it
    out!
    
    Cheers, Laurie.