Re: CiderPress Not Working In Windows 7

[Bill Buckels <bbuckels@escape.ca>]

On Jan 21, 6:19 pm, drkenb <kbuchholz1...@hotmail.com> wrote:
> Maybe instead of making assumptions &
> personal attacks on someone you don't know, you might inquire as to
> why someone would feel that SourceForge is one big black hole and work
> toward correcting that impression if it is wrong.  That would be the
> positive, mature thing to do.

Hi Ken,

I could give a rats-*ss for source-forge or what anyone thinks about
it.

"Microdrive not working in Windows 7" would be just as accurate as the
title of this thread. It sounds to me like Windows 7 is not working
with Legacy Software.

If it were me having the problem, I would see what Microsoft has to
say about it. You seem fine with Mike's solution but the real "fix"
may simply be to handle the mouse differently in the Ciderpress code
for newer Windows versions. Or it may be that a newer compiler may
need to be used.

Over a year ago when Andy McFadden (Ciderpress's Author) and David
Schmidt were putting the finishing touches on the latest version I
attempted to port Ciderpress to Visual Studio 2005 and Visual Studio
2008 without success. Similar experiences by others...


> ----- Original Message -----
> From: "Andy McFadden" <fadden@fadden.com>
> Newsgroups: comp.sys.apple2
> Sent: Monday, December 08, 2008 5:08 PM
> Subject: Re: Ciderpress Possible Problem Reading CP/M Disks
>
>
> schmidtd <schmidtd@my-deja.com> wrote:
>> If someone can make an MS studio solution file that will compile with
>> Visual Studio 2005, I'll volunteer to fix that and maybe even add
>> Apple /// .BA3 file interpretation... but the solution file I got when
>> letting MS "upgrade" it automatically ended in more trouble than there
>> should have been with code that should compile cleanly.
>
> I seem to recall building it with VS 2005 at one point.  I stuck with
> building it from VS 6 because they changed the C++ runtime packaging and
> I didn't want to have to pack-in the additional shared object for Win98
> installs.  Unfortunately that's part of what I lost when the drive head
> assembly decided to go on tour.


What I was able to do to help David and Andy get the last release-out
was to provide what tools were needed to reconstruct Andy's original
build environment. They in turn released the last version of
Ciderpress still using the older compiler.

However there are no guarantees that compiling with a newer compiler
which would be a larger effort than I am prepared to make right now
would solve the problem that you describe. Regardless of your "talent
level", I would argue that if you want to contribute to solving this
problem for others as well as yourself, you can make the effort to
research the problem thoroughly starting with the Microsoft Knowledge
Base because surely you are not the only Windows 7 user having this
problem with Legacy Applications.

My point in mentioning that I can build Ciderpress here so you also
should be able to is a fact and instead of telling us all how
untalented you are, you have my email and could have sent me private
mail asking for some help in building it there yourself and together
we might have explored some debug options with you doing most of the
work. That would be the least lazy and most logical thing to do and an
option that you still have if you can muster the courage to stand on
your own two feet.

If not, perhaps someone else with Windows 7 who is not afraid to run a
C compiler and who would like to try to fix the problem rather than
work-around it can contact me in private mail.

"You can lead a man to slaughter but you can't make him think!"

Bill