Difficulty with new Zoom Floppy

[Stev]

I have a Dell laptop running Windows 10 (home)

Intel dual CPU running at 2.2Ghz, and 4 Gb of ram.

My device manage shows the libusb-win32 device is working.

The xum1541 USB floppy adapter (ZoomFloppy) shows it is working fine, although I had to do the renaming thing and put the dll's and the .sys in the correct directories.

When I reboot, the blue ZF light turns on and off as the laptop shuts down and reboots.

Also the firmware update batch file works so it seems like the laptop is talking to the ZF.

However, when I run the 'runtest' batch file, it responds with "NO PLUGIN DRIVER!: The parameter is incorrect."

Actually, despite the prior indications that it is talking through the USB port to the ZF, it will give you the above response, even when the ZF is unplugged from the USB port.

The final result is that I am trying to get the ZF to communicate with a CBM Model 8050 dual drive.

The 8050 uses the ieee port.

As a secondary question. it seems the ZF ieee connector is wired similar to the x8 parallel edge connector, which would imply that the standard CBM ieee edge connector cable will work. Is this correct or do I need a true ieee-488 cable .

thanks

[Spiro Trikaliotis]

Hello Stev,

* On Sun, Jun 04, 2017 at 06:49:55PM -0700 Stev wrote:

> The xum1541 USB floppy adapter (ZoomFloppy) shows it is working fine, although
> I had to do the renaming thing and put the dll's and the .sys in the correct
> directories.

You "had to do the renaming thing"? What do you mean?

Putting the DLL and SYS in the correct directories does not sound to me
like it could work.

Do you have a working opencbm.conf file? Where? Where did you put the
files into?

Why didn't you use instcbm?

> Also the firmware update batch file works so it seems like the laptop is
> talking to the ZF.

What does it work "works"? What is the output? How does the ZF behave?

> However, when I run the 'runtest' batch file, it responds with "NO PLUGIN
> DRIVER!: The parameter is incorrect."

If you did not run "instcbm xum1541", I am not surprised.

Regards,
Spiro.

--
Spiro R. Trikaliotis
http://www.trikaliotis.net/

[Carsten Jensen]

I'm in the progress of making a combined installer
much inspired by the ZoomFloppy i386 package.

While this is only for amd64, you could try this out.
http://retro-commodore.eu/temp/OpenCBM_and_Tools_amd64_v0.03.exe

Also I'd love to hear some feedback.
/Tomse

[Spiro Trikaliotis]

Hello Carsten,

* On Mon, Jun 05, 2017 at 09:44:25PM +0200 Carsten Jensen wrote:

> While this is only for amd64, you could try this out.
> http://retro-commodore.eu/temp/OpenCBM_and_Tools_amd64_v0.03.exe
>
> Also I'd love to hear some feedback.

From what I have read, it seems to me that the OP has a broken
installation. I think we should find out what he did exactly, and why it
is broken, and try to clean up his machine, instead of putting another
alpha or beta stage "bomb" onto his machine, so we risk having to fix
two broken installs instead of just one.

Just my two cent.

[Steve Gladwin]

Spiro
Starting with file folder named opencbm-ZoomFloopy-2.0-i386
Install batch file was run.
Runtest batch file was run with the following errors
Cbmctrl.exe had an error, I didn¹t write it down
Opencbm.dll was missing.

So, tried firmwareupdate was tried
Error libusb0.dll was missing

Thus opened windrv subfolder
Opened text file libusb-win32-bin-README file
First part says ŒALL ARCHITECTURES: x86\libusb0_x86.dll: x86 32-bit
library. Must be renamed to libusb0.dll
So, nothing done yet. I don¹t have a 32 bit system, mine is 64 bit.
Continuing through README file
In 64 bit systems, installs to Windows\syswow64\libusb0.dll
So, nowhere in the drivers is the libusb0.dll file only file
libusb0_x86.dll

Since it is missing, the inference is that I have to do ³the rename
thing²

Thus libusb0_x86.dll is renamed to libusb0.dll and placed in
\syswow64 folder
Continuing through README file references inf-wizard, binaries, and
AMD64 stuff, none of which seems relevant.

Since opencbm.dll also seemed to be missing, I found it in the \exe
folder and copied it into syswow64 directory
The error for it¹s absence went away

You asked do I have a working opencbm.conf.
Yes. I didn¹t put the files anywhere since there was no error message
pointing to the need for them.

You asked why I didn¹t use instcbm.
I don¹t see it anywhere in the entire install. The only install batch
file I have was the original one mentioned on line two of this email
BUTŠ.
When I review it, I see it calls for
cd exe
Instcbm.exe xum1541
If I review the command line window running the Œinstall' batch file it
states
'Instcbm.exe is not recognized as an internal or external command,
operable program or batch file.¹
All other copy and folder create actions in the Œinstall' batch file
seem to have worked.

Regarding going back to your question regarding opencbm.config
I see it refers to three opencbm dll files. They are still in the \exe
folder and are not in windows\system32 or windows\sysWOW64 since there was
no error message pointing to the need for them to manually transfer.

Regarding your question on the firmware batch file works, the
firmware-update batch file reads the firmware and says it is the most
current. To force it to do the update you should use the -f extension
Originally it had not worked with the error regarding the missing
libusb0.dll file. After previously mentioned manual rename and move, it
worked.
If you run firmware batch file -f, it does the update and flashes the blue
LED once.
So, it appears, during that batch file, to be communicating out the usb
port to the ZoomFLoppy


So, in closing, it seems the issue is the problem with the instcbm.exe
file.
It didn¹t execute and therefore didn't do whatever it was supposed to do.

Regards
Stev



On 6/5/17, 1:38 PM, "Spiro Trikaliotis"

[Spiro Trikaliotis]

Hello Steve,

* On Mon, Jun 05, 2017 at 06:54:38PM -0500 Steve Gladwin wrote:

> Starting with file folder named opencbm-ZoomFloopy-2.0-i386
> Install batch file was run.
> Runtest batch file was run with the following errors
> Cbmctrl.exe had an error, I didn¹t write it down
> Opencbm.dll was missing.
>
> So, tried firmwareupdate was tried
> Error libusb0.dll was missing

I see.

You started installing opencbm (install.bat) *before* installing the
USB drivers. This is the wrong order.

You HAVE to install the USB drivers first, then opencbm.


There is no need to copy files by hand or even renaming them. You have a
very mixed setup now, and it is hard to fix it.


The best thing would be if you would be able to undo everything you have
done. Do you still remember which files you copied to where? Remove
them.


That includes:

1. All files opencbm*.dll from c:\windows and c:\windows\system32 or
c:\windows\syswow64

2. The file opencbm.conf from c:\windows and c:\windows\system32 or


It seems you already installed the USB drivers, right? If you see the
ZoomFloppy in device manager, you must have done it at some point. You
did not write about it, though.


Some detail comments:

> Thus opened windrv subfolder
> Opened text file libusb-win32-bin-README file

That is a mistake. That file is for the one who writes the .inf file
(which is used to install the USB device driver), not for the end user.

> First part says ŒALL ARCHITECTURES: x86\libusb0_x86.dll: x86 32-bit
> library. Must be renamed to libusb0.dll

[...]

> Since it is missing, the inference is that I have to do ³the rename
> thing²

No, no, no, this renaming is done by the device driver installation. The
system selects itself which version is correct.

To be honest, I am not sure if your libusb0.dll is correct at the place,
if you should remove it or not. For the time being, I would leave it "as
is", because you told that xum1541cfg worked (the "firmware updater").

> Since opencbm.dll also seemed to be missing, I found it in the \exe
> folder and copied it into syswow64 directory
> The error for it¹s absence went away

Yes, but you cannot have a working setup until you *write* a correct
opencbm.conf file.

> You asked do I have a working opencbm.conf.
> Yes. I didn¹t put the files anywhere since there was no error message
> pointing to the need for them.

Yes, you have? Or yes, you do not have?

If you have an opencbm.conf file,

1. where is it located (directory)?
2. are there multiple of them? Where (location)?
3. What are their contents?

> You asked why I didn¹t use instcbm.
> I don¹t see it anywhere in the entire install. The only install batch
> file I have was the original one mentioned on line two of this email
> BUTŠ.
> When I review it, I see it calls for
> cd exe
> Instcbm.exe xum1541
> If I review the command line window running the Œinstall' batch file it
> states
> 'Instcbm.exe is not recognized as an internal or external command,
> operable program or batch file.¹
> All other copy and folder create actions in the Œinstall' batch file
> seem to have worked.

instcbm is the important part of the installation process.

Isn't instcbm.exe available in the same directory as the install.bat? Is
it available somewhere else?

In which directory did you unpack the ZIP file in the first place? Is it
on a network share, does any directory on the path have a space (" ") in
it, or is something else weird? Can you give me the exact location (as
seen by cmd.exe, not what the Windows Explorer, the GUI, sees!)

> Regarding going back to your question regarding opencbm.config
> I see it refers to three opencbm dll files. They are still in the \exe
> folder and are not in windows\system32 or windows\sysWOW64 since there was
> no error message pointing to the need for them to manually transfer.

Again, NEVER EVER do you have to transfer anything by hand. If you do
so, you are doing something (very) wrong!

That's the responsibility of instcbm.exe.

> Regarding your question on the firmware batch file works, the
> firmware-update batch file reads the firmware and says it is the most
> current. To force it to do the update you should use the -f extension
> Originally it had not worked with the error regarding the missing
> libusb0.dll file. After previously mentioned manual rename and move, it
> worked.

There was never a prompt that asked you where the drivers for the ZF are
located? I cannot believe that Windows installed the drivers without
accessing the corresponding .inf file. But if it has the .inf file,
there is no need to copy over a DLL or even renaming it, because Windows
takes care of it!

[Stev]

Spiro

Well after getting abused by the developer for not following what would seem obvious, I have two choices.

1) throw it in the trash and write off some money as lost.

2) Or help the developer improve it, and maybe not throw my money away.

So, we'll see how this goes.

I gave you the symptoms of the end result, not the order in which things were done.

You, in turn, answered my symptoms in that order, so we vanish down the rabbit hole.

The order in which things were done was.

1) Unzip file, exactly as the developer created it, no special paths

2) Run 'Install' program (batch file)

    The install program says it installed successfully

    However it also says I have to manually edit the path in order to use the commands from the default folder.

        Done.

3) Run the runtest program..... It fails badly. Big long string of error messages. lots of dll files and sys files missing.

So, the autopsy of what happened.

Your install batch file calls, as its first action, instcbm.exe out of the exe subdirectory

However it fails to run.

The exact message is 'instcbm.exe is not recognized as an internal or external command, operable program or batch file.'

The batch file continues to run, creates directories and copies lots of files successfully.

All of these copy actions cause the CMD window to scroll out of view the failure message,

The only message I see is the end message saying it was successful.

Also it wraps up by saying I have to do some manual work. (fix the PATH).

Done.

Another nugget.

If you don't intend the end user to manually move, copy or rename some files, then don't put the instructions in a README file.

I don't know why it was there, but if all goes pear shaped, and it did, it seemed to offer some level of guidance, intended for someone.

There was already a direct instruction to manually do something (fix the PATH)

I have totally reloaded the windows system from a backup.

Redone steps 1,2 and 3 from above, and it all still does not work, with all of the original error messages.

Stemming back to the simple error that the instcmd.exe xum1541 is not recognized, for a reason I do not know.

How do we fix that, or achieve its desired result.

Stev

 

 

[me...@gmx-topmail.de]

Hello Stev,

have you installed the Windows driver as described in the "ZoomFloppy-Manual.pdf", section "B. Plug in the ZoomFloppy via USB and install the Windows driver" ?

It would help if you could provide a screenshot of your Windows device manager showing the ZoomFloppy device.

 

When I look at what went wrong with your setup it might be best if you could start from a fresh system backup again without any ZoomFloppy related traces.

-Arnd

 

Gesendet: Mittwoch, 07. Juni 2017 um 02:47 Uhr
Von: Stev <skgl...@suddenlink.net>
An: "ZoomFloppy Users" <zoomflop...@googlegroups.com>
Betreff: Re: Difficulty with new Zoom Floppy

--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Carsten Jensen]

I agree with you that a cleanup of his system is a good idea.

This is of course when cleanup is finished and to help OP
getting his installation up and running afterwards.


Cheers
Carsten

[Spiro Trikaliotis]

Hello Stev,

* On Tue, Jun 06, 2017 at 05:47:30PM -0700 Stev wrote:

> Well after getting abused by the developer for not following what would seem
> obvious, I have two choices.
> 1) throw it in the trash and write off some money as lost.
> 2) Or help the developer improve it, and maybe not throw my money away.

If my words made you think I wanted to abuse you, I have to assure you
that this was not my intention. I am very sorry if you feel like this.

BTW, I am not the developer of the ZF. ;)


Arnd already gave you a hint what might be wrong:

> The order in which things were done was.
> 1) Unzip file, exactly as the developer created it, no special paths
> 2) Run 'Install' program (batch file)
>     The install program says it installed successfully
>     However it also says I have to manually edit the path in order to use the
> commands from the default folder.
>         Done.
> 3) Run the runtest program..... It fails badly. Big long string of error
> messages. lots of dll files and sys files missing.

As stated by Arnd, you have to install the drivers (from the directory
windrv) as stated in the manual, BEFORE you come to number 2.

This is very important!

> So, the autopsy of what happened.
>
> Your install batch file calls, as its first action, instcbm.exe out of the exe
> subdirectory

It's not my install batch file, it's the one from the ZF developers. ;)
My tool is instcbm.exe.

> However it fails to run.
> The exact message is 'instcbm.exe is not recognized as an internal or external
> command, operable program or batch file.'

And this is especially weird. Did you get another message, for example,
a message box, which tells you that libusb0.dll (or another file) is not
found?

Can you try to run the command-line instcbm xum1541 from a command shell
and give me the exact output?

> The batch file continues to run, creates directories and copies lots of files
> successfully.
> All of these copy actions cause the CMD window to scroll out of view the
> failure message,
> The only message I see is the end message saying it was successful.

Unfortunately, the install.bat file does not test the return value of
instcbm. Otherwise, it might stop and tell you that there was a problem.

> Also it wraps up by saying I have to do some manual work. (fix the PATH).
> Done.

You're right. I executed it some times, but I could not remember that it
tells you to fix the path.

> Another nugget.
> If you don't intend the end user to manually move, copy or rename some files,
> then don't put the instructions in a README file.
> I don't know why it was there, but if all goes pear shaped, and it did, it
> seemed to offer some level of guidance, intended for someone.

The problem: The device driver uses libusb, a library for accessing USB
devices. This library is used by OpenCBM to access the xum1541 device -
that is, OpenCBM does not provide its own driver for the USB access.

The README file you are referring to is from the libusb project.
Currently, I am not sure if the license of libusb requires us to include
it, but in any case, it is considered "good practice" to include such
files, so that people know what was contributed by which project. That's
why these README files are included verbatim.

> Stemming back to the simple error that the instcmd.exe xum1541 is not
> recognized, for a reason I do not know.
> How do we fix that, or achieve its desired result.

Can you please

1. try after installing the device driver (cf. the mail from Arnd)
2. give me a screenshot of the output of instcbm?

I do not have an Windows 10 system at hand, and even my test
installation for Windows 8 does not work ATM (I don't know why), so I
cannot test myself, unfortunately.

Does anybody else on this mailing list have a Windows 10 machine and can
tell if instcbm.exe has a problem on this OS?

[Spiro Trikaliotis]

Hello again,

* On Wed, Jun 07, 2017 at 09:43:46PM +0200 I wrote:

> Can you try to run the command-line instcbm xum1541 from a command shell
> and give me the exact output?

I just got my Windows 8 test machine working again.

What I found out is that I cannot read the output of instcbm, because it
opens it in another Window.

It would be best if you would change the rules: Start an console with
administrator right (Win + X, and then choosse "command line
(adminstrator)" or similar; I am sorry, I have only a german version of
Windows here, so I cannot tell you the exact name). Then change to the
directory where you unpacked the OpenCBM package, and run install.bat
from there.

Give me the complete output you got, so I can analyse it.

[Stev]

ok. I we have soldiered through the open salvo, and now we are getting down to business. It's all ok.

Thanks for your guidance although this group posting thing makes it weird to keep see past posts in the middle of current posts.

Actually finding where I post my response was a challenge.

However, here is where it gets weird and maybe someone will say that my system is doing  the right thing, but to me, it is weird.

Also, I am the only user of this laptop so my user status is 'administrator'

I am not sure if this an antivirus program thing but if it is, it is certainly handling things differently than it ever has before

So, taking the two suggestions and doing them both.

1) run instcbm.exe xum1541 from outside the install batch file and.

2) run it from an administrator command shell.

Both ways sort of have the same pseudo wacky outcome.

1) running it via windows, it says you can't do this because you have to be administrator.

..... then instcbm.exe vanishes.

2) running it from the command shell, it says 'access is denied'

..... then instcbm.exe vanishes.

So it appears to give a similar 'denied access' error message, and it vanishes.

I am not using the word delete because it does not appear in the recycle bin.

So I have unzipped the original file a few times and now have a copy stored elsewhere so it doesn't 'delete' it.

I have not looked anywhere special to see if opencbm-x**1541.dll files appear anywhere because it doesn't appear like it is doing anything.

I am out of time for tonight.

Tag, your it.

[Carsten Jensen]

Did you try the installer I posted earlier?
http://retro-commodore.eu/temp/OpenCBM_and_Tools_amd64_v0.03.exe
There are no i386 version yet

Also there are atleast 2 installation packages that uses an install.bat
file, which one are you trying to install?
OpenCBM Aplha 4.99.98
or
the ZoomFloppy i386 v2 package?

It might be easier to help you knowing which installation file you are
using.
The OpenCBM Alpha version is very well hidden and you'll have to
know what to google for to find it. So My guess is that you are using
the ZoomFloppy i386 version?
I think Spiro might believe you are using the Alpha and tries to help
you there -correct me if I'm wrong-.

As you say this thread is somewhat messy as it's out of order,
this is quite weird for a google group as it usually is in good order.
Having said that, if you've already posted which package you've
installed. I appologize, though I haven't seen that.

As a visual help, it would help a lot if you could record your desktop
to show what you do step by step.
VLC or Open Broadcaster Software can do this (I prefer OBS rather than
VLC for this).

Cheers
Carsten

> --
> You received this message because you are subscribed to the Google
> Groups "ZoomFloppy Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to zoomfloppy-use...@googlegroups.com

> <mailto:zoomfloppy-use...@googlegroups.com>.

[me...@gmx-topmail.de]

Hello Stev,

can you please tell me what your Windows UAC security setting (User Account Control) is?
On Windows 8 64bit I had this setting under "Control Panel -> User Accounts -> Change User Account Control Settings".

If I remember correctly I turned UAC off (lowest slider setting / "Never notify") and *restarted* the computer. Then I extracted the ZoomFloppy files to a hard disk directory and started the install-script/instcbm from a "command prompt" as Spiro said (e.g. "instcbm xum1541").

-Arnd

 

[nhoijtink]

Often when exeutables vanish and cannot be found in the Recycle bin, this is done by a virusscanner/malware scanner. Once it has moved, the filesystem cannot find it anymore and gives you the denied error message.

I would suggest (temporarily) disable all malware/virusscanners, to see if the vanishing stops, and from there try to figure out what scanner has a false positive report.


Op donderdag 8 juni 2017 03:08:34 UTC+2 schreef Stev:

[Spiro Trikaliotis]

Hello Stev,

* On Wed, Jun 07, 2017 at 06:08:34PM -0700 Stev wrote:

> Also, I am the only user of this laptop so my user status is 'administrator'

As Bob Reid has written, you must use a special version of the command
shell, nevertheless.

> I am not sure if this an antivirus program thing but if it is, it is certainly
> handling things differently than it ever has before

To be honest, having a look into your description (file "vanishes"), I
would think that it is an AntiVirus thing.

What AntiVirus are you using? Does it have the possibility to see in a
log what it has done? Perhaps, it has some "quarantine" where
instcbm.exe has be put into, and you can get it from there?

> Both ways sort of have the same pseudo wacky outcome.
> 1) running it via windows, it says you can't do this because you have to be
> administrator.
> ..... then instcbm.exe vanishes.

So, you do not have administrator rights. This explains the error
message, but it does not explain why the file vanishes.

> 2) running it from the command shell, it says 'access is denied'
> ..... then instcbm.exe vanishes.

This sounds extremely like an AntiVirus!

As "nhoijtink" has written, can you temporarily disable the AntiVirus?
But DO THIS ONLY IF YOU ARE SURE YOU HAVE TAKEN THE opencbm ZIP file
from the ZF homepage!

> I have not looked anywhere special to see if opencbm-x**1541.dll files appear
> anywhere because it doesn't appear like it is doing anything.

It could not have done anything, as it has not even started to run.

[Spiro Trikaliotis]

Hello Carsten,

* On Thu, Jun 08, 2017 at 08:34:05AM +0200 Carsten Jensen wrote:

> Also there are atleast 2 installation packages that uses an install.bat
> file, which one are you trying to install?
> OpenCBM Aplha 4.99.98
> or
> the ZoomFloppy i386 v2 package?

Stev already answered it in one of his first mails, it is the ZoomFloppy
package.

> I think Spiro might believe you are using the Alpha and tries to help
> you there -correct me if I'm wrong-.

You're wrong. :p

> As you say this thread is somewhat messy as it's out of order,
> this is quite weird for a google group as it usually is in good order.

I let my mail program handle this. I do not use the Google web
interface. It's a mailing list in the end, and what else but a mail
program can handle a mailing list?

[Tregare]

On Thu, Jun 8, 2017 at 2:37 PM Spiro Trikaliotis <an-zoomfl...@spiro.trikaliotis.net> wrote:

Hello Stev,

* On Wed, Jun 07, 2017 at 06:08:34PM -0700 Stev wrote:

> Also, I am the only user of this laptop so my user status is 'administrator'

As Bob Reid has written, you must use a special version of the command
shell, nevertheless.

Spiro is correct, even as an an admin user you still have to launch command shell specifically granting admin privs(run as administrator) because they assume most people will mess up their systems with admin privileges.  Think of it as the windows equivalent of the unix SUDO command.

If the program is trying to write to system directories it HAS to be run as administrator (/windows/... /Program Files(x86)/... / Program Files/... the ellipses signify the subdirectories therein. ) there may be more but I forget.

--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.

[Stev]

SUCCESS.

Sort of. We aren't done yet.

SO I know a few people had suggestions, thanks.

But I was still following up on a prior suggestion.

I had to Google how to open a CMD window, especially to run as administrator.

Which I did.

Then I ran instcbm.exe xum1541

It still failed.

BUT....

Now my Norton Antivirus software opened a window that said it aborted the program and quarantined the file.

The reason it said it quarantined it was due to 'a file with Low Volume Reputation'

Basically, globally, only a few hundred uses of it had been recorded and thus it was unknown.

Not really a threat, just an 'unknown'

This was the first time the popup had ever open saying what was occurring

So, I enabled it.

It ran, see record below.

I don't have time tonight to continue with using the drive to test things, I will do that over the weekend.

So, we have progressed forward in a positive way.

As another item, there was one dll (opencbmvdd.dll) I never moved because there was never an error message saying it was needed.

Also, I see it thinks it is Windows NT. I guess your detection didn't know what future processors would be

Stev

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Stev\Desktop\CBM Pet\ZoomFloppy\opencbm-ZoomFloppy-i386\exe>dir
 Volume in drive C has no label.
 Volume Serial Number is 0240-C86E

 Directory of C:\Users\Stev\Desktop\CBM Pet\ZoomFloppy\opencbm-ZoomFloppy-i386\exe

06/08/2017  06:33 PM    <DIR>          .
06/08/2017  06:33 PM    <DIR>          ..
06/07/2017  07:46 PM            30,848 cbm4nt.sys
06/07/2017  07:46 PM            29,440 cbm4w98.sys
06/07/2017  07:46 PM            29,440 cbm4wdm.sys
06/07/2017  07:46 PM            36,864 cbmcopy.exe
06/07/2017  07:46 PM            34,304 cbmctrl.exe
06/07/2017  07:46 PM            17,408 cbmformat.exe
06/07/2017  07:46 PM            19,456 cbmforng.exe
06/07/2017  07:46 PM            21,504 cbmrpm41.exe
06/07/2017  07:46 PM            40,960 d64copy.exe
06/07/2017  07:46 PM            27,136 d82copy.exe
06/07/2017  07:46 PM             9,728 flash.exe
06/07/2017  07:46 PM            22,528 instcbm.exe
06/07/2017  07:46 PM             9,728 morse.exe
06/07/2017  07:46 PM            40,960 nibconv.exe
06/07/2017  07:46 PM            55,808 nibread.exe
06/07/2017  07:46 PM            38,912 nibrepair.exe
06/07/2017  07:46 PM            49,152 nibscan.exe
06/07/2017  07:46 PM            50,176 nibwrite.exe
06/07/2017  07:46 PM            24,064 opencbm-xa1541.dll
06/07/2017  07:46 PM            17,920 opencbm-xu1541.dll
06/07/2017  07:46 PM            20,992 opencbm-xum1541.dll
06/07/2017  07:46 PM            22,528 opencbm.dll
06/07/2017  07:46 PM            12,288 OpenCbmVDD.dll
06/07/2017  07:46 PM            11,264 rpm1541.exe
06/07/2017  07:46 PM            19,456 samplelibtransf.exe
06/07/2017  07:46 PM            45,056 xum1541cfg.exe
              26 File(s)        737,920 bytes
               2 Dir(s)  166,464,069,632 bytes free

C:\Users\Stev\Desktop\CBM Pet\ZoomFloppy\opencbm-ZoomFloppy-i386\exe>instcbm xum1541
Access is denied.

C:\Users\Stev\Desktop\CBM Pet\ZoomFloppy\opencbm-ZoomFloppy-i386\exe>instcbm xum1541
You're using Windows NT 6.02.
I do not know it, but OpenCBM should work, anymore.
Working directory = 'C:\Users\Stev\Desktop\CBM Pet\ZoomFloppy\opencbm-ZoomFloppy-i386\exe\',
system  directory = 'C:\WINDOWS\system32\',
driver  directory = 'C:\WINDOWS\system32\DRIVERS\'.
Copying '.\opencbm.dll' to 'C:\WINDOWS\system32\opencbm.dll'
Copying '.\opencbmvdd.dll' to 'C:\WINDOWS\system32\opencbmvdd.dll'
Using plugin: 'xum1541' with filename 'opencbm-xum1541.dll'.
++++ Install: 'xum1541' with filename 'opencbm-xum1541.dll'.
Copying '.\opencbm-xum1541.dll' to 'C:\WINDOWS\system32\opencbm-xum1541.dll'

C:\Users\Stev\Desktop\CBM Pet\ZoomFloppy\opencbm-ZoomFloppy-i386\exe>

[Stev]

So, the correct source of all the irritations is my anti virus software which has a feature called 'Download Insight'

A further dig says it bases an executable on it worldwide reputation.

So, not really say there is a virus, just say that an executable has such small worldwide reputation that it COULD be a virus.

So, in speaking honestly, anything these days that is developed to support an 30-40 year old operating system probably does not have much of a world wide audience.

Having fixed it, the cbminst.exe install activities now worked properly.

BUT. yeah, you guessed it. RUNTEST and all other commands now get quarantined.

So, I have to dig into Norton and work out how to exclude these folders from the Download insight quarantine function.

And, in case your worried Spiro has embedded a real virus, I have faith he doesn't. But this is a project laptop that has no email access, no account access and no social media access. So, if it gets trashed, I don't really care.

But I think we will get this to work.

Later

Stev

 

[nhoijtink]

Glad your were at least able to find a direction to a solution. I haven't used Norton for years, but i was allways possible to exclude files/folders from the scan.


Op zaterdag 10 juni 2017 02:37:42 UTC+2 schreef Stev:

[Stev]

Spiro

So, we have now advanced in a positive way.

I had to wire my own ieee connector to the x6 header.

Now runtest.exe produces

 

Found the following drives:
 8: 8250 dos2.7

You should see your drive detected above. If not, please see the
ZoomFloppy manual for troubleshooting tips.
Press any key to continue . . .

However I find none of the OpenCBM commands work.

Further review explains that OpenCBM, CBMLink, C1541, Nibtools and ImgCopy are all intended for different drives or different communications methods .

Since I am using the IEEE port to a CBM 8050 drive, I should be using IMGCOPY.

However the link to IMGCOPY is broken.

Can you supply correct directions to it, or better guidance on commands to use for the IEEE method of transfer to the CBM 8050

Stev

[Silver Shroud]

Hello,
Installing this fixed all of my problems! I'm even able to use it in VirtualBox under Arch Linux!
Does this installer have a permanent home and has it been updated recently?
Thanks,
Silver Shroud.

On Thursday, 8 June 2017 15:34:09 UTC+9, Carsten Jensen wrote:

Did you try the installer I posted earlier?
http://retro-commodore.eu/temp/OpenCBM_and_Tools_amd64_v0.03.exe

There are no i386 version yet.

[Carsten Jensen]

There is a OpenCBM_and_Tools_amd64_v0.05.exe

just replace the 3 with a 5 in the same link.

Make note that this installer (which is compiled by me) is not supported by Spiro (developer of OpenCBM)

though the only difference is the path and added tools like nibtools etc.

If you want support from Spiro, I'd suggest you install OpenCBM ny hand using the files on his website, and reading the manual

how to install it.

cheers

Tomse

--

You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Virus-free. www.avast.com

[Spiro Trikaliotis]

* On Sun, May 06, 2018 at 04:33:35AM -0700 Silver Shroud wrote:
> Hello,
> Installing this fixed all of my problems! I'm even able to use it in VirtualBox
> under Arch Linux!

Huh? The installation of the Windows package should not have *any*
impact on running it on a virtualised Linux. This should have worked
without any hazzle in the first place.

[Silver Shroud]

I'm not interested in installing using the official package. I followed the directions. Please don't ask me how because I did it 20 times whilst reading the manual.
It installs to C:\Program Files\opencbm\ and the initial scripts point to C:\opencbm\bin\ . Modifiying or duplicating or installing files in different locations doesn't help.
Yes, I'm installing the drivers first then installing the package.

My point is, I couldn't get the official package to work properly with XP, 7 or 10.
Plus, the Linux package doesn't build properly in Arch Linux whether I build directly from git or use one of the AUR packages.
The Windows installer worked straight away. It just works. I'm happy.

If you're not happy, then please don't tell me.

[Spiro Trikaliotis]

* On Sun, May 06, 2018 at 03:10:28PM -0700 Silver Shroud wrote:
> I'm not interested in installing using the official package.

Where did I meantion the official way? I did not.

> Plus, the Linux package doesn't build properly in Arch Linux whether I build
> directly from git or use one of the AUR packages.
> The Windows installer worked straight away. It just works. I'm happy.

I am just telling that you are mixing two things: The Windows installer
does not help you in installing it in Arch Linux, even if it is running
in a VirtualBox container under Windows.

Please do not spread such FUD.


I did not tell anything else.

[James Ziegelmueller]

I think you are getting upset over nothing. Of course I'd be able to use it in a VM if the official installer actually worked.

I was just remarking that I was able to use it in a VM. Sorry if the connected sentence confused you.

I am not looking for an argument. Let's all be happy.

--
You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-users+unsubscribe@googlegroups.com.