Conference gyro::internet_toolss

I've installed it on a system where the C: was tiny, and on a system where the 
C: drive is large. Works fine.

PJDM

Thanks - on Alpha, or Intel?

Greg.
[posted by Notes-News gateway]

Actually, when you say "C was tiny", was it still the 
system disk? In my case, C is NOT the system disk - it
is only the boot disk (i.e it only has the boot partition).

Greg.
[posted by Notes-News gateway]

	I've done this with no problem on an Alpha.  You shouldn't be installing
  ANYTHING on C:, it's only useful as a boot partition.  Look to see where IIS
  is installed.  It may be confused.  Try installing ODBC separately from
  IIS.

		Danny

	Check to see if your environmental variables point to anything
	on C:. (like TEMP pointing to C:\TEMP)

							mike

I checked the environment variables - nothing point to drive C:,
and TEMP & TMP point to D:\TEMP.

Thanks,
Greg.
[posted by Notes-News gateway]

>	I've done this with no problem on an Alpha.  You shouldn't be installing
>  ANYTHING on C:, it's only useful as a boot partition.  Look to see where IIS
>  is installed.  It may be confused.  Try installing ODBC separately from
>  IIS.

In *this* case, yes, C is only the boot partition. Is that the normal
practice? I (perhaps obviously ;) haven't had much experience with
NT yet,  but on a system that I built once, I had D as the boot 
partition, and C as the system drive. I am wondering whether 
ASP is trying to install the ODBC stuff to drive C, i.e, whether
drive C is hard coded into the kit somewhere.

The IIS content is installed to another drive again (F), also with
plenty of free space. The install found the content directory without
any problems, and installed it's own content etc.   If you mean
the IIS system related files, then they are on the main drive (D).
After saying that, though, I seem to have another problem, where
ASP files can't execute  - "HTTP/1.0 500 Server Error (The specified
module could not be found. )".  Things are in a mess, aren't they.
(btw other scripts run ok - it's only ASP that seems to have the
problem. So I think the permissions in the content area are ok).

I have not yet tried to install ODBC from a kit other than the Active 
Server Pages kit. I have tried checking just the ODBC subset
though, and it still fails. 

Thanks,
Greg.

  



>
>		Danny

[posted by Notes-News gateway]

I wrote:

>After saying that, though, I seem to have another problem, where
>ASP files can't execute  - "HTTP/1.0 500 Server Error (The specified
>module could not be found. )".  Things are in a mess, aren't they.
>(btw other scripts run ok - it's only ASP that seems to have the
>problem. So I think the permissions in the content area are ok).

Regarding that problem, I have solved it at least. I have included
below my post to  the msnews active server pages forum. 

Greg.
---------------------------------------------------------------------------
I have fixed this error.

The problem was, I think, due to another problem I have with
installing ASP, and which I have reported in this forum.
The first time I attempted to install ASP, it failed when it
got to the stage of installing the ODBC subset. 
Now, it seems that this also caused the ASP core
components to not be  installed. Even when I reinstalled
ASP without selecting the ODBC subset, it didn't fix the
problem. 


I noticed that system32\inetsrv\ASP\components existed,
but there were no actual files in that folder.
So what I did was to remove system32\inetsrv\ASP....
and reinstall ASP, without selecting the ODBC subset.
ASP is now working.

I think the ASP kit install needs to be made more robust.

Regards,
Greg.
Digital Equipment Corporation
[posted by Notes-News gateway]

    I have ASP installed on an Alpha with D as the WINNT disk and E as the
    IIS disk and the ODBC installed fine.
    
    Try installing the ODBC SDK (download from Microsoft) and see if that
    installs OK.
    
    Keivn

I installed the ODBC SDK - it installed without any problems.

I just discovered that D (the WINNT disk) was actually FAT, 
rather than NTFS. I have converted it to NTFS, but I still
have the same error when installing ASP.

Thanks,
Greg.
[posted by Notes-News gateway]

I have discovered that the system drive had it's drive letter
changed after installation. (E:\... was scaterred all through
the registry - it should of course be D:\...)

Substituting D: for E: in the registry has fixed another
problem I had. (couldn't install Internet Explorer).
I assume that it will also fix this problem - I will
try tonight. No further reply from me means that it
worked.

Thanks for the help, and sorry if this topic doesn't
belong here (in hindsight, it's more of an NT problem
than an Internet Tools problem).

Greg.

p.s Arrrghhhh!!!

BTW, E: is a CD-ROM drive. ;)