V0.9 differences for WinXP?

Asked by william kranz on 2018-02-21

Sorry, I'm old school and have several XP systems I use for testing things. Just getting into Win32 API programming and wanted to use this source code as a model as I am having issues accessing anything except for a:, my floppy. Don't know 'source forge' but I could not find the V0.9 source code. However I did see a note that said for WinXP one should use the V0.9 executable so I assume there is some real difference. Anyone remember this? My interest is in reading foreign, ie incompatible with Windows, medai either floppies or thumb drives. Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Image Writer Edit question
Assignee:
No assignee Edit question
Solved by:
Tobin Davis
Solved:
2018-02-21
Last query:
2018-02-21
Last reply:
2018-02-21
Best Tobin Davis (gruemaster) said : #1

The source and binary files for all releases are at https://sourceforge.net/projects/win32diskimager/files/Archive/. You can also clone the git repo and checkout at the various release tags, although technically the v0.9 release tag is off by one (I updated the readme on the very next commit with the release number and changes).

From v0.9 to v1.0, there were some api changes that are only available in the new releases of Windows. Rather than having spaghetti code that would have to check which version of Windows the user was running, I chose to drop XP/Vista support. The idea is to keep the code small and clean. That also meant that a lot of the bug fixes that went into newer versions are not available to XP, like USB Floppy detection, and the rewrite of drive detection.

While it wouldn't be too hard to fork a branch for XP and cherry pick some of those fixes, I chose not to as I really have limited time to do any development work on the main code, let alone support another branch. Also, I lack any systems capable of running XP except in a VM, which doesn't really allow for much real testing.

If you want to explore forking the main tree from v0.9 into an XP edition, I would be happy to support your efforts with the limited time I have available.

william kranz (willytk) said : #2

Thanks Tobin:I may explore the older code a little, but I am not ambiguous enough to want to do a fork.  I was curious about the web page comment about XP and felt there might be some significant API change after WinXP.
I have been a small open source developer for a long time and totally agree with your not wanting spaghetti code.  If its just that functions you use have been added to the Win32 API since XP, then I get it.  I do also have one Win10 system I can test on.
Just to amuse you, I started on PCs with MSDOS in the mid 80s but also did a lot of PDP-11 work to help support my Dad.  I just got the Win10 64 bit system, and it won't even run 16 bit code.  So late in life I am forced to explore the Win32 API.I do most of my work in Linux these days as I don't really like the evil Microsoft Empire because they want to be paid for the OS.

Impressed that you were able to create/maintain such a cross platform program.  Great job.Thanks for the link to various source code distributions, as I said its been a while since I've used 'source forge' and its changed some!
Be well

    On Wednesday, February 21, 2018, 10:16:58 AM EST, Tobin Davis <email address hidden> wrote:

 Your question #664762 on Image Writer changed:
https://answers.launchpad.net/win32-image-writer/+question/664762

    Status: Open => Answered

Tobin Davis proposed the following answer:
The source and binary files for all releases are at
https://sourceforge.net/projects/win32diskimager/files/Archive/. You
can also clone the git repo and checkout at the various release tags,
although technically the v0.9 release tag is off by one (I updated the
readme on the very next commit with the release number and changes).

>From v0.9 to v1.0, there were some api changes that are only available
in the new releases of Windows.  Rather than having spaghetti code that
would have to check which version of Windows the user was running, I
chose to drop XP/Vista support.  The idea is to keep the code small and
clean.  That also meant that a lot of the bug fixes that went into newer
versions are not available to XP, like USB Floppy detection, and the
rewrite of drive detection.

While it wouldn't be too hard to fork a branch for XP and cherry pick
some of those fixes, I chose not to as I really have limited time to do
any development work on the main code, let alone support another branch.
Also, I lack any systems capable of running XP except in a VM, which
doesn't really allow for much real testing.

If you want to explore forking the main tree from v0.9 into an XP
edition, I would be happy to support your efforts with the limited time
I have available.

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/win32-image-writer/+question/664762/+confirm?answer_id=0

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/win32-image-writer/+question/664762

You received this question notification because you asked the question.

william kranz (willytk) said : #3

I now understand the difference between V0.9 and 1.0 and understand how to find the older source code. thanks