okay running win2000 and trying to upload a kernal (hijack) i am getting the following message

awaiting prompt then


error: No prompt within timeout


Thankys anybody

Greetings!

Double check your cable and connections. Make certain nothing else is connected on your serial port as well. It sounds like you are not getting connectivity.

What software is being used to send the kernel? If it is my logo editor, go through everything here to make sure that you can communicate with the player at all on the serial port. Make sure you can send and recieve text with Hyperterminal. If that works, then the logo editor should work.

If you are not using my logo editor, then use my logo editor.

/me re-reads the title of the thread and realizes that you were using logo edit. Sorry.

If you're having serial problems, you could use Hijack's FTP server to store it to /proc/empeg_bootlogos. But you probably want to get your serial working anyway (for next time you have to put Hijack onto a new official player release).

[Hmm, wonders... - it must be possible to remove the kernel chunk from an Empeg *.upgrade file, leaving Hijack in place providing /proc/empeg_kernel, and never needing serial again. Didn't smu write a packager? What would be really cunning would be to write an unpackager to run in the player kernel so we could send an upgrade file to /dev/empeg_upgrade and have it write the disk partitions etc. Not sure that it would work while the kernel is running, though.]

If you're having serial problems, you could use Hijack's FTP server...

I believe that he's attempting to install hijack via the serial cable after upgrading to beta13. So he can't use FTP until after Hijack is installed. Chicken and egg, get it?

In reply to:

---

I believe that he's attempting to install hijack via the serial cable after upgrading to beta13

---

Oops, I shouldn't believe that I can remember everything with a quick glance at the subject line. My advice is only good for uploading logos (or, by using /proc/empeg_kernel, kernels) with Hijack already operational.

But the good side is that you (thinfourth) know that your serial connection works, as you managed to apply the Empeg upgrade file. Chances are, you're suffering one of the usual annoyances, like having some other process holding onto the port.

okay i can send logos and i can also connect via hyperterminal

any clues tony ?

Try removing the power from the player and applying power only when prompted by the software.

If that doesn't work, try running it on a different PC.

Ah ha i have got it

Logoedit don't like it when you are getting a file from another computer over a network, we my network at least.

Being lazy sod downloaded hijack to computer connected to net directly and then used laptop to upgrade, copied file to laptop and then there was no probs. Another day and another bit of knowledge.

i really needed to put hijack on for a really important reason buggered if i can remember what it was though

Ah, yeah, it won't like UNC paths for the kernel file.

You could do it across the network if you mapped a drive letter.

and how do i map a drive letter?

right click my computer. click map network drive. enter unc path

Right click on Network Neighborhood and select "Map Network Drive".

It amazes me that Windows is such a piece of crap that you're having this much trouble just simply parsing a file name.

Edit: And it's not like this is the only thread today on Windows filename parsing. There's at least one other.

I'm not having trouble parsing a file name.

It's the command-line interpreter that feeds the file name to the UPLOAD.EXE code. Command-line code under Windows is all old throwbacks to DOS, which didn't have network UNCs. You can't send a network UNC path to an old command-line app, at least not without a lot of special-case code.

Ideally, I would completely remove the UPLOAD.EXE command line applet and have the logo editor grab the COM port directly and do all of the handshaking work itself. If I did that, then there wouldn't be an issue.

However, that's a lot of work. It was easier just to use the existing DOWNLOAD.C code from Hugo and recompile it for Win32 with an extra parameter. That's what made the difference between Logo Editor becoming a reality and being just a dream. If I'd had to rewrite all the serial communications protocol stuff, I wouldn't have ever finished it. Maybe not even started it.

So, as a result, my code has to mash the path down to a short-file-name that's acceptible to pass on the command line to DOWNLOAD.C. And if it's a UNC, it can't mash it into a short-file-name (by definition).

Hence the error when trying to work with UNCs as fed to UPLOAD.EXE.

Like I said. Piece of crap.

(BTW, I wasn't implying that it was your fault or the fault of your program.)

Sorry to bring an old topic up but I have had the same trouble tonight. I think I have figured it out.

Logoedit will not find the Command Prompt if the upgrade file is on a read only network share. I could not get it to work in any way, shape or form. But then I ran upload.exe manually (from the command prompt) and it worked. I figured that 'Command Prompt' was the promt that couldn't be found. I then copied the hijack file the the local computer and uploaded it no problem with Logoedit -- success. Then I tried changing permissions on the share to allow read and write access to the share with the hijack file and then applied across the network and voila! It worked!

So there you go... it seems that it has no problem with network shares... as long as they are read and write shared.

Just thought I'd share this with you all, and you as well Tony... maybe a small change you can make so this problem doesn't rear it's ugly head again.

René

It tries to convert the path to the file into a "short file name", i.e., drive letter, colon, backslash, and 8.3 file names. It does this because the command line to the "download.c" code is space-delimited and won't take long file names. If it's on a network share that doesn't have an assigned drive letter (it's being accessed with the UNC beginning with a double back slash), the short filename conversion won't work. Are you sure it was because the network share was read-only, or was it because you mapped a drive letter to that network share at some point and it worked after that?

No drive mapping involved whatsoever. I simply shared my downloads folder with write permissions and logoedit now works fine. I don't have a single mapped drive on my home network.