PTP

[villa...@gmail.com]

I don't know at what point  the error has crept in but I have gone back to run the martini PTP again as per the video: THN036 - New #IMSAI8080 esp desktop UI & firmware.

My 'tapes' folder is at latest version.
When I drag the magmarti.ptp on to the PTR it shows 'load (lots of num&letters).png and not the filename.ptp.  If I drag the same file from the desktop (win10-Chrome) onto the PTR it loads OK (correct name) BUT when I run it, it stops before it reaches the actual data because it has quite a long blank leader.

Both conditions are repeatable.

I have loaded the dzmation.hex onto the glyph ok. Rebooted (no roms - 64k mem) - dazzler comes up with cursor image.
I wonder if anyone has same problem using the latest beta version.?.

[TheHighNibble]

3nd attempt!

I've tested on my setup and I'm not having these problems.

It's not clear to me what you mean when you say:

• When I drag the magmarti.ptp on to the PTR it shows 'load (lots of num&letters).png and not the filename.ptp
  

Can you break that down and maybe provide an example/image?

You also say:

• BUT when I run it, it stops before it reaches the actual data because it has quite a long blank leader.

This is typical if the PTR: is sending data but the IMSAI isn't asking for any data, so the websocket buffer overflows.

I suspect you have not made the change to the boot.conf required for dazzlemation to use the PTR:

• SIO1.portA.device=WEBTTY,UART0

needs to be changed to

• SIO1.portA.device=WEBPTR,WEBTTY,UART0

This enables the PTR: to send data to the standard "console" ports on the IMSAI

[villa...@gmail.com]

Many thanks, it runs correctly now - for some reason either omitted or changed the setting 

• SIO1.portA.device=WEBPTR,WEBTTY,UART0  .....................but only by dropping the magmarti.ptp from the desktop on to the PTR

However I still have the problem with the .png instead of .PTP  being loaded on to the PTR - I searched on my file browser for the particular xxxx.png file and its actually the png for the pink tape icon !!!

I tried it on my laptop as well and get the same problem. 

On my main pc, using CCcleaner, I cleared all internet cache, cookies etc etc but no change.  The drag and drop from the Tape window moves the png (icon) instead of the PTP file.

I'm using Win10 chrome - as I haven't run this for quite awhile I don't know where the problem first occurred.

[TheHighNibble]

When you open the SYS: window, what is the GUI Version given in the first, About box?

It is possible it is the file in your TAPE: library: what happen when you drag that "tape" over the download glyph at the top of the TAPE: window - it will download to you PC downloads - what file do you end up with?

[villa...@gmail.com]

webfrontend-v1.13.0-beta.11
The download to pc is correct i.e magmarti.ptp

[TheHighNibble]

Weird. I have had a few other people report problems with drag-and-drop (of disks) being affected by Chrome Extensions they have installed.

Can you disable your extensions, or log into Chrome as the guest user to see if this makes a difference.

[Tom Wilson]

I have also never gotten the drag and drop from the tape library to the PTR to work. I can drop files from my Windows desktop, but as the person above said, when I drop the icon from the tape library, it drops the PNG icon, not the file associated with the icon. 

Tom Wilson
wils...@gmail.com
(619)940-6311 

--
You received this message because you are subscribed to the Google Groups "IMSAI 8080esp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to imsai8080esp...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/imsai8080esp/7cbc94b9-4380-4720-95f1-61fd6571ddd7n%40googlegroups.com.

[TheHighNibble]

Thanks. Tom used a magic word in his post - "Windows" - that got me thinking...

Who would have guessed that drop events in Chrome behave differently under Windows to macOS - bad design Google Chrome!

My dev machine is macOS  and I could not reproduce the problem.

My under-used Windows test machine reproduced the problem exactly.

I have a solution that has tested out well. I will include it in the next BETA version of the Desktop UI in the next few days.