Hi Rugxulo, > On Jan 7, 2023, at 7:41 PM, Rugxulo <[email protected]> wrote: > > Hi, > > On Wed, Jan 4, 2023 at 4:11 PM <[email protected]> wrote: >> >> Due to some changes at the current registrar I use for my SHIDEL.NET domain, >> my email was broken for the last week or so. >> >> If any of you attempted to contact me or if I missed something that required >> my attention, I would not have received any messages. So if there is >> anything you need to point out to me, you will need to resend it. > > Glad you're doing okay.
Thanks. Hope you are well as well. > > Yeah, I sent one trivial email (that bounced), but since you're busy I > don't think it's super important to resend. I even had to re-verify myself to the freedos-user list from having to many bounced emails. ... Yep, been very busy working on a new DOS project. Something that I’ve wanted to do for decades. A few weeks after I started it, there was around 350kb of assembly sources. When all of a sudden, weird crashes developed. And I mean really weird. For example, printing the letter ‘a' as a single character to STDOUT, a crash would occur in a completely unrelated area of the program. Change nothing but the letter ‘a’ to ‘b’, it would crash in a different unrelated section program. Trace all the instructions, stack usage, etc in that simple print, the crashing sections and other places… No bugs detected. Crazy making. After a couple days of head banging, I found that I pushed an aspect of NASM past a breaking point into unreliability that compiled as garbage. So, I spent a couple days working out the best way to get the results I wanted and not encounter the issue. At that point, I could have spent about a week modifying my existing code. But instead, I decided to completely refactor it and make some additional improvements and optimizations alone the way. Three weeks later, I’m about 90% done with the code refactor and back to the point I was at roughly a month ago. It is working great and the source code is even more awesome than before. At least I’m fairly certain the original problem was caused by the issue with NASM that I found. But, there could have been some dumb typo I failed to notice prior to the refactoring. But, the NASM issue does exist, can be demonstrated and was defiantly at least part of the problem. The issue is rather obscure and not easy to explain. But, it is reproducible. > Thanks again for your work on FreeDOS, and don't stress too much in > the New Year. Happy New Year :-) _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
