After the booting, if the OS is fully loaded, most likely the network setting for operational mode are in some plain text file. Here you have the possibility to do the in-place editing, as in the bootloader, or mount the image in Linux and edit the file with a text editor. If the drive is using VxWorks filesystem is a pain, because while the horny Linux mounts almost everything , for the vxWorks miserable FAT bastardization there is a separate kernel module that needs to be compiled individually. I suffered with this while trying to restore and update the storage of Tektronix AWG that is documented somewhere else on the forum.
But, all in all, it may be simpler and easier to add other IP to the PC that is used to control the printer to fit with whatever address it needs.
Cheers,
DC1MC
Its weirder then that. It wasn't the network or the printer, Vx or any settings...it was the PC!
I spent hours trying to get it to work on my windows 7 32 bit computer, it just kept causing the Vx on my printer to crash.
Loaded up the software on a win2k laptop (which after a fall is less than happy to be alive) and it just works.
No crashes at all, even with the new bootrom. It has to just be that computer.
The printing application while designed for NT and 2000, usually works fine on win7 32 bit.
But this is a strange implementation of the printer. The previous models used a DEC AXP vme board (running Vx) and not a 486.
I was given some contact details of the developer and I will reach out and see if he still remembers and maybe has the source.
Im not sure what kind of file system is on that drive. Im dreading it to be honest.
On the older machines (they're older by a few years), the drive is only used to store/buffer the image being printed (probably a tiff), an image config (probably txt) and the LUT (also txt).
In the event that those scsi drives fail and they do, just pop in another one, assuming you can find a drive that is in better shape.
It usually doesn’t even have to be formatted. It just overwrites whatever what was on it. An interesting way to do it but its worked for 25 years.
I switched the spinning rust out for SCSI2SD V6's and its amazing, no more high pitched whining or the sound of marbles rolling around.
But this one is an PATA and evidentially stores something important.
I will try to bring up a linux box and DD a clone. Hopefully I don't mess that up