be careful as post#815 i re-copy here
In my case the target nam had to be this name i mentioned, because TekScope would be buggy or would not start
This is what works for me in the nvram content
boot device : sm
processor number : 0
host name : host
file name : c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.1:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00
host inet (h) : 192.168.0.1
gateway inet (g) : 192.168.0.2
user (u) : anonymous
ftp password (pw) : anonymous
flags (f) : 0x1000
target name (tn) :
tds7000 -----> i've been told to keep it like this, if not, TekScope doesn't save some settings ??
startup script (s) : c:\vxBoot\topscript.hw
other (o) : 0x0
Still have doubts on the flags and other sections,
if i put something else in the flag like 0x1008, tekscope stalls
if i change other setting like 0x1000 TekScope starts but no traces of ch1 ch2 ..... cant recall what i put ...
![Face Palm :palm:](https://www.eevblog.com/forum/Smileys/default/facepalm.gif)
----------------------------------------------------------------------------------------------------------------------------
The dbFsIoctl: invalid code 3 error you have, may come from the topScript.hw file
thread at :
https://www.eevblog.com/forum/repair/boot-problem-on-tektronix-tds7404-scope/ it direct to lines like :
cd "dbfs:c:/vxBoot"
dbfs:c:/vxBoot