LV 6i Network Installation question

[L. Ravi Narasimhan]

I have a data acquisition system based on a networked single-board
computer with a hard disk running W98SE. I put LV5.1 on this system
when it was "apart", ie. not tightly integrated into its present
housing and LV runs on it just fine.

I have purchased LV6i and wish to install it over the network as
disassembling the SBC to add a cd-rom would be very difficult. On a
separate PC running W2k I can see the SBC, map its hard drive (C:) to
the W2k machine (G:). For a test, I added and deleted files on the
SBC's drive from the W2k machine without any difficulty.

I have tried to install LV6i onto the SBC using the W2k machine's
CDROM drive and the network. I tell it to install into G:\Program
Files\National Instruments (replace the de
fault C: with G:) The LV
installer can see the mapped drive, subdirs, etc. When it attempts to
begin the installation, the hourglass icon shows up and the installer
hangs. W2k's task mgr shows the app as "Not Responding"

I have gone to the SBC and explicitly shared (what I think are) the
required directories and subdirectories but this does not seem to
help. I've also google-searched the web for this issue and gone over
NI's support database with relevant keywords and come up empty.

Advice/suggestions including "No chance at success" would be greatly
appreciated.

Sincerely,


Ravi Narasimhan
Dept. of Physics, UCLA
oski@physics.ucla.edu

[MichaelAivaliotis]

If I understand you correctly, it sounds like you are running the installation on one machine to install it on the other. This is the wrong approach. The best way to do the installation is to copy ALL the install files to the SBC's hard drive and run the install from the SBC's hard drive.

If you don't have enough HD space then the next bet would be to map the remote CDROM so that the SBC can see it as a mapped drive, then run the install on the SBC.

In any case you have to run the installation on the computer that will be the final destination.

[L. Ravi Narasimhan]

On Sat, 10 Nov 2001, Michael Aivaliotis wrote:

> If I understand you correctly, it sounds like you are running the
> installation on one machine to install it on the other. This is the
> wrong approach. The best way to do the installation is to copy ALL the
> install files to the SBC's hard drive and run the install from the
> SBC's hard drive.

Yes, that was indeed the goal but your suggestion makes more sense.
If I understand correctly, you recommend essentially replicating the
CD-ROM's contents/file structure onto the SBC's drive. If so, this should be do-able
and I'll try it.

> If you don't have enough HD space then the next bet would be to map
> the remote CDROM so that the SBC can see it as a mapped drive, then
> run the install on the SBC.

Actually, this was the first thing I tried: Attempting to get the
SBC(W98) machine to see the W2k desktop's CD-ROM. There is some
critical issue with W98 <-> NT/W2k networking that I have not been
able to comprehend/solve. The W2k/NT machines on my network do not
need passwords to see one another's shared filesystems. In order for
my W98 SBC to see the network drives, I have to supply a password upon
booting into W98. So, I can see the other machines on the network this way. But,
when I try to access explicitly shared directories on the NT/W2k
boxes, W98 asks me for some network password that does not exist. If
I bypass the login request, I can't see the networked drives on the SBC.
There is no way that I've been able to find whereby I can get around
this problem.

The reason I attempted to do the remote install W2k -> W98 is that I
can transfer files from W2k desktop to the W98 SBC without any
difficulty. I assumed (incorrectly) that by mapping the SBC disk to
the W2k box that all would go transparently.

This, of course, is way off-topic for an LV group. Scouring the W98
groups and MS websites has not turned up a suitable solution just yet.

> In any case you have to run the installation on the computer that will
> be the final destination.

Thanks for the suggestions and I'll try them out, promptly.

Sincerely,

--- Ravi Narasimhan


---
Ravi Narasimhan
Dept. of Physics and Astronomy, UCLA
http://www.physics.ucla.edu/~oski

[L. Ravi Narasimhan]

On Sat, 10 Nov 2001, Michael Aivaliotis wrote:

> If I understand you correctly, it sounds like you are running the
> installation on one machine to install it on the other. This is the
> wrong approach. The best way to do the installation is to copy ALL the
> install files to the SBC's hard drive and run the install from the
> SBC's hard drive.
>
> If you don't have enough HD space then the next bet would be to map
> the remote CDROM so that the SBC can see it as a mapped drive, then
> run the install on the SBC.
>
> In any case you have to run the installation on the computer that will
> be the final destination.

I followed your first suggestion and everything worked perfectly for
both LV6i and the 6.0.2 upgrade/patches. Thanks very much for t
he
timely advice. Disassembling that system to temporarily add a CD-ROM
would have been a major chore.

Sincerely,

--- Ravi Narasimhan

---
Ravi Narasimhan
Dept. of Physics and Astronomy, UCLA
http://www.physics.ucla.edu/~oski