Hijack 288 to v320

Ok i read threw the threads and i still can't get it to install. I looked at the 300versions and it appears to me as though its a manual type in install and if this IS NOT the case can someone please give me the "laymens terms" of what i need to do to get this 320 ver.

thanks
shawn

Not sure I understand the question.

Download version 320, run the latest version of my Logo Editor, and select "Kernel Upgrade Utility". Is that not working or something?

yeah that was kinda sketchy......ok Im run logo editer 1.7 and i downloaded v320.hijack.v200b13.mk2.zImage and i went to kernel flash utilities and selected v320 to be installed and i received a "Error number 53 occered in the kernel routine" i am using a serial and RJ45 ports and tried all different configs of the cables but it won't get sent........but the cables work on Emplode and jemplode?

Error 53 is a "File Not Found", I think.

Did you make sure to unzip all the files that go with the logo editor (not just the main EXE)?

Where on your hard disk did you unzip it?

Where on your hard disk is the .zimage file for the kernel, and what is its file name?

What operating system are you running?

Can you install a boot logo?

Have you checked to make sure the serial port is even working?

well i canget my car logos downloaded to the logo editer i think im gonna do a completly new download of the hijack ......thanks for your help as usual

shawn

ok i got it figured out what my dumb a$$ did..........I didn't unzip the "upload" part of the logo editer.......I'll get this damn computer stuff figured out one of these days..........thanks again for your help ......the few minutes you spent on this thread is very apprieceated

Thank You,
Shawn

I didn't unzip the "upload" part of the logo editer..

Heh. The very first thing in my list of possible problems after seeing "error 53".

I'll get this damn computer stuff figured out one of these days

Best tip for computer novices: When one is experiencing problems and asking the experts for help, reporting the exact steps you took to make the problem happen, along with an exact description of the problem itself (especially the exact text of any error messages) is very important. Once you said "error 53", I knew where to start looking.