rloew

Well, I got most of these. I know I have the rest, I've seen them but they weren't in the stuff I had easily accessible.

I have yet to go through stuff on what I think are his testing machines. I have plans for doing that mid next week though. I can use this info (knowing that there might be an RFDISK 3.1) to help me figure out if I'm looking at something more recent than what I am working off of.

The biggest issue is that he just has so much data and replication of data. It's hard to find things. I remember the HP drivers. He was a bit of a data hoarder! Good point about the compatibility issue. It would suit him for everything to be as minimalist as possible. Makes me wonder if the SSL certificate is a problem or not. Thank you for this. Feel free to upload and spread around whatever materials of his you have. It's the only way to keep it alive. I attached makewrap.cpp, is that what you referred to? He liked very simple tools for things like debugging. I'm honestly surprised I haven't found anything for debugging over serial yet. I found stuff related to two other compilers today. I haven't found out where he actually built his code though. I haven't changed anything so my dad's license is still there. But, the intention is that the code is public. I would hope people who build off the code give some credit to my father but that is up to them. makewrap.cpp

I think I'll have to set up one of his computers to find it. I have a feeling it isn't in the "active" set of stuff I'm looking at. Thanks! Uploading them without going through them would not be a good idea. Right off the bat, there is customer information scattered in there. I already seen some family photos in the mix and even some code that I know is not relevant. I wouldn't want to just throw it out there. I can hold my own in regards to programming knowledge so that isn't a concern. A repo can be made at any point and anyone here could do it if they felt inclined to do so. I can't offer support for it anyway - I just don't have the time. My option was to upload source without a build system or to not upload source. I would like to think you can see what the better option is. In any case, the logic in the code is more important for anyone to try to learn or extend his work. Regarding who my dad was, I'm uploading his resumes so you get an idea of what he felt was appropriate to say he did. He did a bit of consulting work for Aerospace Avionics (I think that is the name, I have a pile of hardware schematics from them but they were absorbed into another company) but pretty much was consulting for the last 30 years and living off investments and tax liens. My dad was phone phreaker in his youth and actually got arrested for it (I'm quite proud of him for that) and was forced to write a public apology to avoid jail time. He was also responsible for this article: http://explodingthephone.com/docs/dbx0431.pdf I'm pretty sure that I'm about the only person he would trust with this. Although, he would not be pleased that I'm just giving away his work and that is a point where we differed in opinion, I think it is the best option for me to preserve his legacy. I never got into Windows like my dad did but I do take after him quite a bit. I wish my dad followed more modern standards for organization and such but the major issue is that there is just a massive amount of data. I brought about 60TB of stuff back home with me and that might only be half of his recent stuff (last few years). He has tape archives going back at least 20 years but I am pretty confident that stuff isn't related to his Windows endeavors. HTML by hand fits my dad so well. But I'm thinking about using React for the long-term of the page. Newspaper Article for Rudy.pdf resume.txt RESUME.DOC

The site is live. I'm going to post some of his packages onto it today. If you'd like me to link to you as a supporter/mirror/whatever, just let me know. I found that drive he purchased and I couldn't read it on my own machine, I haven't gotten around to seeing if it would read on one of his own. I did a quick grep for SCSI and WD in his source folder (at least the one that I think has everything) and attached what I found. I don't think this is the relevant portion though. I'll keep it in mind when I'm looking through things though! INT1587.C SCANHDC.C

You are welcome to put something up. I just got the rloewelectronics.com domain that I'll put everything on as I sort it out. Reading your post, I think he had given me a copy of Borland's Turbo C compiler at some point. It does seem like he had some sort of custom handling of his includes.

Thank you, I've been in touch with @LoneCrusader regarding his cotnact with my father. I appreciate what you've done with my dad's account. I have found some source code, lots of it, so I know some of it isn't related to his patches. I'm going to make that stuff available too once I actually have some free time (my life was already busy before all of this). @LoneCrusader mentioned to me that he might have been using a custom compiler which I am unaware of at the moment so it may not just compile nicely. But, I've attached a few of the TRIM named files (and what look like dependencies he had) that I have. I don't know if these are the most recent or even if they are the right ones! BLK13EX.C TRIMCHK.C TRIMCMD.C DISKPORT.C TRIM.C DRIVE.C IDENTIFY.C GETNUM.C

I am glad that he had found friends here. I never really knew the extent of all of his Win9x work. My current desktop can still boot into Win9x because of him, although, I haven't in a while. I would like to try to provide some closure for others so I'll give a timeline of what happened. You may or may not have known that my father had heart issues. He had a mild heart attack in his 40s. August 19th: Goes in for angiogram, gets fast tracked for triple bypass surgery. He left me a message midday about it and I called him that evening. We discussed the options they gave him and he seemed settled on the bypass surgery. August 21st: Has the surgery. Gets out of surgery, doctor tells me take he handled it well. August 24th: First time I was able to contact him on the phone after the surgery. He seemed well but certainly worn-down after the surgery. August 25th: Had a heart attack (cardiac event). Survived, but apparently it was not a good situation. I was able to talk to him that evening (I think, it could have been the next day). Got the impression that his diabetes and insulin resistance played a major role in the incident. August 28th: Last night I get to talk to him. I made plans to come down to see him on the 30th. August 29th: Situation escalates, possible infection/sepsis. August 30th-September 2nd: He is heavily sedated for the pain. But things seem stable. Not good, but stable. I return home and hope for the best. September 3-7th: Situation goes back and forth, fluid buildup leads to treatment for infection. Ultimately, the infection is treatable but the sepsis is not. September 9th: Palliative care nurse contacts me and I go back down that afternoon. Situation is getting worse. September 10th: Responsiveness to questions during sedation vacation is lost except to pain stimulus. September 11th: Taken off of life support. Passes at 1:28pm. I hope that helps. I think it has helped me to write it out. I forgot I had the message from him in my voicemail about going to the hospital. My own personal take on it is that complications from diabetes played a major role in his inability to recover but I am not a doctor and it's just my own mind trying to justify the situation.

I didn't realize that people would find out so soon about my father's passing. I wanted to express my appreciation of the impact he has had for many of you with all his work on Windows. I got to hear about it for years over meals and I never realized how many people found value in his patches. It is a busy time right now but I did want to clear the air regarding the patches. I would like them to continue to be distributed, for his work to be remembered and to be beneficial to others. So, please, freely distribute what you may have in terms of the work my dad did. When things are more settled, I will see what I can do regarding anything missing he might have had available and whatever relevant material there might be that someone could use to further pursue his work.

DOS has a simpler implementation of FAT32 than Windows 9x. I was able to Patch it to work up to 32K. VFAT only supported 2K until I Patched it for 4K. Above 4K I think there are issues with Caching since Caching is done by Memory Pages which are 4K. I have identified two internal variables that don't have valid values when larger Sectors are used.

Apparently for all versions of Windows. Patched DOS can go to 32KiB Sectors for a maximum of 128TiB per Partition. Patched 9x can support Drives larger than 16TiB but with a maximum Partition size of 16TiB.

I decided to take the plunge. I tried 8K and 16K Sectors. Neither worked in XP. CHKDSK did seem to understand and repair a NTFS Partition. Formatting failed for either FAT32 or NTFS. WD Formatter could reset and reformat the Drive. Windows 2000 rebooted when I connected the Drive with 16K Sectors. Windows 8 doesn't support 16K Sectors. Windows 98SE did not support 16K Sectors even after further patching of VFAT. Raw access was available, as well as ASPI so I can set or reset the Drive as needed. My RFDISK and RFORMAT tools can handle 16K Sectors as they were designed to support up to 32K Sectors.

It is not currently on my website, you can contact me directly. I will list it if I see more interest. It is called ALIGNDRV.

Done.

It is possible to add AHCI Boot to an Installed IDE system as well as the reverse. The former is documented on the Internet. I plan to add NVME to the options in the future.