possible vxworks issue

My problem: I work for an overseas company which supplies terminals to industry. Older terminals use vxworks. We are a satellite of this company so getting support on vxworks is difficult. FYI I have a linux/unix background but no vxworks.

When a PCI card becomes suspect I simply flash the firmware back onto the card using a burner attached to a PC. I am not sure which OS the PC is booting into - it has *nix type features. (I think) I have stuffed up the script which supervises the process.

Can anyone identify the OS and help me to fault find?

• During boot I see "Vxld 1.2" which suggests to me it is booting into vxworks
• After booting I get a prompt "->" (my quotes)
• To get into the correct directory I type "cd /abc/bin"
• To initiate the script I type "<load.sh"
• I got nosy and typed "cat load.sh"
• Since this point, "<load.sh" simply returns a blank line and back to the command prompt

I am loath to type anything more based on the problems I (may) have created. If this is vxworks can anyone suggest how to dump the file and/or edit it?

that's my needle in a haystack. Any help appreciated.

Is load.sh a symbolic link to another file? If so maybe you have to find the other file and work on it.

Does "file load.sh" work? That should tell you what kind of file it is.

Does "strings load.sh" work? That should show you any ascii characters contained in the file that may be masked by control characters.

Barring those, you may be able to see it using the od (octal dump) command.

Thanks MensaWater but it looks like I have deleted the file/removed the symbolic link. I don't know what I did so I think I will quit while I am only a little behind. Hopefully a colleague will simply pass across the files so I can restore them

The syntax you show is consistent with a vxWorks shell. None of the commands mentioned by MensaWater are on any vxWorks system I've used. From what media does your PC boot (I've only ever used tftp to boot vxWorks across a network)? I think vxWorks recognizes FAT filesystems. You might be able to mount the media on a Linux host and find a '~backup copy' of the file. I don't know what 'cat' might have done. In the vxWorks shell, any filename arguments (most command arguments) have to be enclosed in "double quotes".

--- rod.