just imported some files from the original code and
had to modify the sources file for the windows DDK,
VisualDDK did most of the hard lifting, I just had to
spend hours in trial and error mode.
All I really did was compile it for x64 - for now
that's the limit of my contribution.
Well.. from everything I've found - which there is a lot of confusing information-Proper driver signing should be the first step to get this code out of the door.
it seems like only certain certificate authorities are allowed to distribute certificates
suitable for signing kernel-mode code. Some results say VeriSign is the only one but
I think that is no longer the case, though the list is still limited.
Certificates seem to be good for a year, but cost at least $200 USD up to $499
for VeriSign; this is for ones that can sign Kernel-Mode code, Also it seems like
you have to be incorporated or similar to get Kernel-mode signing certificate;
at the very least you have to go through a bunch of background checks and
supply ID, Bills with your(or the company's) address, tax information, etc. Also
you need a domain that is owned by you(or your company that's applying).
I'm unclear on whether you have to get Microsoft's WQHL testing and pass.
There is a discount provider for certificates that is $95 a year, comodo
but thier certs are not approved for kernel mode code.
Research Sources:
http://www.sysprogs.org/signing/
http://stackoverflow.com/questions/2847 ... -windows-7
http://successfulsoftware.net/2008/02/2 ... te-ripoff/
http://forums.comodo.com/code-signing-c ... 728.0.html
http://www.osronline.com/showthread.cfm?link=145563
http://codefromthe70s.org/kernelsigning.aspx
http://www.osronline.com/article.cfm?article=465
http://codesigning.ksoftware.net/
http://blog.ksoftware.net/
http://support.godaddy.com/help/7351/re ... ertificate
http://www.godaddy.com/ssl/code-signing ... icate.aspx
http://www.digicert.com/code-signing/ke ... icates.htm
http://www.symantec.com/verisign/code-s ... thenticode
http://msdn.microsoft.com/en-us/windows ... e/gg487317
http://msdn.microsoft.com/en-us/library/ff548231.aspx
http://msdn.microsoft.com/en-us/library/ff552299.aspx
http://msdn.microsoft.com/en-us/library/ff552289.aspx
http://msdn.microsoft.com/en-us/windows ... 87315.aspx
http://msdn.microsoft.com/en-us/library/ff552275.aspx
http://technet.microsoft.com/en-us/libr ... 10%29.aspx
I have never used a cvs(besides typing the command into mingw earlier from theSource code is maintained at a CVS repository. Currently our member Myrd has access to the code. For the code to be included into the source, it would need to be supplied as patches to the current code, or perhaps (in the case of this stand alone driver) as a separate directory that could be included (with a description of how to build/sign the driver).
You can communicate about the code on the Basilisk/SheepShaver development mailing list, accessible here: https://lists.sourceforge.net/lists/lis ... lisk-devel
compiling guide); so I know almost nothing about them. From reading some of
the messages on the cvs earlier, I take it patches are usually submitted as
a 'diff' which I assume is a file containing only new/different text in source
code. However I didn't change any source code - yet. Which the drivers for
the network aren't even in the cvs source. Which should be fixed I think.
The source package I got (build 142?) contains driver source
for windows 95/98 real mode(dos) cd drivers, as well as a win9x b2ether
vxd source and windows nt4 b2ether source and the NT5(2k/XP) source.
--Edit--You must be bold by now You mean you've given up on cd support? A skeleton driver is available from the disassembled code.... I placed links to all function calls that are in the sys driver, thus hopefully making it possible to reconstruct the driver. You can have that code. (I'll post it here in a new topic).
By the way.. how did you disassemble the code? I mean what tools did you use?
--End Edit--
No, not giving up at all, just need to take a break from it.. you can only sit there and
pull your hair out and feel like your accomplishing nothing for so long before you have
to step away and come back later with a fresh perspective. Also I just really really want
to actually write some code and do something for a change, I feel like I haven't really done
much at all yet; Though I may be too rough on myself, because I have a lot of things
I'm learning or doing for the first time.
Like I said before, I don't feel the classes I took adequately prepared me,
though I didn't finish my degree(yet but I want to); I did take two Visual Basic
and two C++ classes and pass them all. Didn't finish the java class; partly because
of other circumstances and partly because I just had a really hard time with the
teacher's assignment methods. He had some good ideas, but the way he implemented
them was so inefficient and tedious, and he required it for every project. I spent
more time in word than writing code and actually learning. There is a lot more
than that but I don't wanna bore you.
Yeah, I can't seem to find good documentation on the prefs format and options,This is a awsome idea! It would work great as long as it adheres to the prefs files format.
HFS is read by cdenable.sys (hint but also by Apple's boot camp drivers. I know of no free libs for windows.
is it listed anywhere or do I just have to use trial and error or crawl the code?
Also build specific options are needed.
--Edit--
Thought I should note I plan on implementing support for each emulator/build in plain text,
with an ini file of sorts, as well as a plain text ini prefs definition for each emulator.
So in theory, anyone can add profile support for additional emulators, or builds.
I also plan to have a in program Wizard/GUI for doing this, as an 'advanced user' feature.
--End Edit--
As for the HFS read/write - I was thinking more disk image creation/management,
sort of like HFV Explorer, but upgraded and integrated and with automated capabilities.
That's why I was hoping for a library of some sort.
As for CD stuff I'm hoping to find a user mode way, but I am not giving up on
the cd driver either, but no matter what it likely won't help with hfv disk images.