Re: [ros-dev] [ros-diffs] [cgutman] 52055: [FDC] - Implement fdc.sys (still needs work but fairly complete) [TXTSETUP.SIF] - Load fdc.sys for floppy controllers [FDC.INF] - Install fdc.sys for floppy controllers
With all my respect to the hard work put into this, I want to express my concerns:
Why is there a need to develop a half-done fdc, if there is a full, working, tested by millions driver available even in old DDKs, which we can use without violating its license? Why waste time writing that driver from scratch now when we could just import DDK's one and spend time fixing our PnP manager instead, and other involved components so that DDK's driver actually works? Again, with all my respect to Cameron, he does a great job, but when he disappears next time for a year or two, who is going to finish FDC? Or any other of his half-finished branches? (each being really a pearl if it's done).
I would really suggest using all available resources first and only then spend time developing our own stuff instead of already existing.
Thanks for understanding, Aleksey.
On Jun 2, 2011, at 10:24 AM, cgutman@svn.reactos.org wrote:
Author: cgutman Date: Thu Jun 2 06:24:25 2011 New Revision: 52055
URL: http://svn.reactos.org/svn/reactos?rev=52055&view=rev Log: [FDC]
- Implement fdc.sys (still needs work but fairly complete)
[TXTSETUP.SIF]
- Load fdc.sys for floppy controllers
[FDC.INF]
- Install fdc.sys for floppy controllers
Added: trunk/reactos/drivers/storage/fdc/CMakeLists.txt (with props) trunk/reactos/drivers/storage/fdc/directory.rbuild (with props) trunk/reactos/drivers/storage/fdc/fdc/CMakeLists.txt (with props) trunk/reactos/drivers/storage/fdc/fdc/SOURCES (with props) trunk/reactos/drivers/storage/fdc/fdc/fdc.c (with props) trunk/reactos/drivers/storage/fdc/fdc/fdc.h (with props) trunk/reactos/drivers/storage/fdc/fdc/fdc.rbuild (with props) trunk/reactos/drivers/storage/fdc/fdc/fdc.rc (with props) trunk/reactos/drivers/storage/fdc/fdc/fdo.c (with props) trunk/reactos/drivers/storage/fdc/fdc/pdo.c (with props) Modified: trunk/reactos/boot/bootdata/txtsetup.sif trunk/reactos/drivers/storage/CMakeLists.txt trunk/reactos/drivers/storage/directory.rbuild trunk/reactos/media/inf/fdc.inf
With all my respect to the hard work put into this, I want to express my concerns:
How did I know this was coming? ;)
Why is there a need to develop a half-done fdc, if there is a full, working, tested by millions driver available even in old DDKs, which we can use without violating its license? Why waste time writing that driver from scratch now when we could just import DDK's one and spend time fixing our PnP manager instead, and other involved components so that DDK's driver actually works?
As far as I know, the only floppy related DDK driver is sfloppy.sys. If that is wrong, I would be happy to import a better fdc.sys and scrap this one.
Again, with all my respect to Cameron, he does a great job, but when he disappears next time for a year or two, who is going to finish FDC? Or any other of his half-finished branches? (each being really a pearl if it's done).
aicom-hardware-fun can be deleted because somebody is finally working on usb. tcp-rewrite-branch was merged to the GSoC project. The only incomplete branch is aicom-network-branch which has Alex's new Winsock code in it (which only a few bugs prevent from being fully functional).
I would really suggest using all available resources first and only then spend time developing our own stuff instead of already existing.
I did this thing in one (long) night because I was bored. It's not like I spent a month doing it. I know people say "Who cares about floppy support?" and I agree but it has to be done at some point to be compatible with XP/Vista/7.
Thanks for understanding, Aleksey.
Regards, Cameron
" I know people say "Who cares about floppy support?""
I care
Because i do think ReactOS can bring back to life old computers, which still have floppies
On Thu, Jun 2, 2011 at 5:53 PM, Cameron Gutman cameron.gutman@reactos.orgwrote:
With all my respect to the hard work put into this, I want to express my
concerns: How did I know this was coming? ;)
Why is there a need to develop a half-done fdc, if there is a full,
working, tested by millions driver available even in old DDKs, which we can use without violating its license?
Why waste time writing that driver from scratch now when we could just
import DDK's one and spend time fixing our PnP manager instead, and other involved components so that DDK's driver actually works? As far as I know, the only floppy related DDK driver is sfloppy.sys. If that is wrong, I would be happy to import a better fdc.sys and scrap this one.
Again, with all my respect to Cameron, he does a great job, but when he
disappears next time for a year or two, who is going to finish FDC? Or any other of his half-finished branches? (each being really a pearl if it's done). aicom-hardware-fun can be deleted because somebody is finally working on usb. tcp-rewrite-branch was merged to the GSoC project. The only incomplete branch is aicom-network-branch which has Alex's new Winsock code in it (which only a few bugs prevent from being fully functional).
I would really suggest using all available resources first and only then
spend time developing our own stuff instead of already existing. I did this thing in one (long) night because I was bored. It's not like I spent a month doing it. I know people say "Who cares about floppy support?" and I agree but it has to be done at some point to be compatible with XP/Vista/7.
Thanks for understanding, Aleksey.
Regards, Cameron _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
I care since I use 5¼inch floppies. And of course once ReactOS is stable enough I intend to replace the current operating system on it (Windows NT Workstation 4.0) as better stuff will run on it.
And I also have two drives.
I agree ReactOS can bring back to life old computers, or at least give them a more up-do-date feeling to it.
On Fri, 03 Jun 2011 02:20:51 +1000, Javier Agustìn Fernàndez Arroyo elhoir@gmail.com wrote:
" I know people say "Who cares about floppy support?""
I care
Because i do think ReactOS can bring back to life old computers, which still have floppies
On Thu, Jun 2, 2011 at 5:53 PM, Cameron Gutman cameron.gutman@reactos.orgwrote:
With all my respect to the hard work put into this, I want to express
my concerns: How did I know this was coming? ;)
Why is there a need to develop a half-done fdc, if there is a full,
working, tested by millions driver available even in old DDKs, which we can use without violating its license?
Why waste time writing that driver from scratch now when we could just
import DDK's one and spend time fixing our PnP manager instead, and other involved components so that DDK's driver actually works? As far as I know, the only floppy related DDK driver is sfloppy.sys. If that is wrong, I would be happy to import a better fdc.sys and scrap this one.
Again, with all my respect to Cameron, he does a great job, but when
he disappears next time for a year or two, who is going to finish FDC? Or any other of his half-finished branches? (each being really a pearl if it's done). aicom-hardware-fun can be deleted because somebody is finally working on usb. tcp-rewrite-branch was merged to the GSoC project. The only incomplete branch is aicom-network-branch which has Alex's new Winsock code in it (which only a few bugs prevent from being fully functional).
I would really suggest using all available resources first and only
then spend time developing our own stuff instead of already existing. I did this thing in one (long) night because I was bored. It's not like I spent a month doing it. I know people say "Who cares about floppy support?" and I agree but it has to be done at some point to be compatible with XP/Vista/7.
Thanks for understanding, Aleksey.
Regards, Cameron _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Hi,
Actually it is src\storage\fdc\ in the DDK. The ISO is freely availably from Microsoft. Import it and see if it works with PnP.
Sfloppy is only in the WDK, which you are NOT allowed to use in ReactOS.
-- Best regards, Alex Ionescu
On 2011-06-02, at 11:53 AM, Cameron Gutman wrote:
With all my respect to the hard work put into this, I want to express my concerns:
How did I know this was coming? ;)
Why is there a need to develop a half-done fdc, if there is a full, working, tested by millions driver available even in old DDKs, which we can use without violating its license? Why waste time writing that driver from scratch now when we could just import DDK's one and spend time fixing our PnP manager instead, and other involved components so that DDK's driver actually works?
As far as I know, the only floppy related DDK driver is sfloppy.sys. If that is wrong, I would be happy to import a better fdc.sys and scrap this one.
Again, with all my respect to Cameron, he does a great job, but when he disappears next time for a year or two, who is going to finish FDC? Or any other of his half-finished branches? (each being really a pearl if it's done).
aicom-hardware-fun can be deleted because somebody is finally working on usb. tcp-rewrite-branch was merged to the GSoC project. The only incomplete branch is aicom-network-branch which has Alex's new Winsock code in it (which only a few bugs prevent from being fully functional).
I would really suggest using all available resources first and only then spend time developing our own stuff instead of already existing.
I did this thing in one (long) night because I was bored. It's not like I spent a month doing it. I know people say "Who cares about floppy support?" and I agree but it has to be done at some point to be compatible with XP/Vista/7.
Thanks for understanding, Aleksey.
Regards, Cameron _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
You can also check out http://www.hackchina.com/en/r/101589/fdc.htm__html as an HTML reference.
The nice thing about FDC is that it even uses ACPI, so it's a good test point for that.
Then you can import flpydisk and get rid of the current NT4-based floppy.sys
-- Best regards, Alex Ionescu
On 2011-06-02, at 11:53 AM, Cameron Gutman wrote:
With all my respect to the hard work put into this, I want to express my concerns:
How did I know this was coming? ;)
Why is there a need to develop a half-done fdc, if there is a full, working, tested by millions driver available even in old DDKs, which we can use without violating its license? Why waste time writing that driver from scratch now when we could just import DDK's one and spend time fixing our PnP manager instead, and other involved components so that DDK's driver actually works?
As far as I know, the only floppy related DDK driver is sfloppy.sys. If that is wrong, I would be happy to import a better fdc.sys and scrap this one.
Again, with all my respect to Cameron, he does a great job, but when he disappears next time for a year or two, who is going to finish FDC? Or any other of his half-finished branches? (each being really a pearl if it's done).
aicom-hardware-fun can be deleted because somebody is finally working on usb. tcp-rewrite-branch was merged to the GSoC project. The only incomplete branch is aicom-network-branch which has Alex's new Winsock code in it (which only a few bugs prevent from being fully functional).
I would really suggest using all available resources first and only then spend time developing our own stuff instead of already existing.
I did this thing in one (long) night because I was bored. It's not like I spent a month doing it. I know people say "Who cares about floppy support?" and I agree but it has to be done at some point to be compatible with XP/Vista/7.
Thanks for understanding, Aleksey.
Regards, Cameron _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-
Adam -
Aleksey Bragin -
Alex Ionescu -
Cameron Gutman -
Javier Agustìn Fernàndez Arroyo