Jump to content

denodster

6502
  • Content Count

    33
  • Joined

  • Last visited

Everything posted by denodster

  1. I've got one of these. It has the Apple Confidential stickers on the roms, and the big cap. The caps were leaking so had them replaced and the big cap is now a different big cap.
  2. do either these cards work in your IIci?
  3. You could try unseating the cpu and reseating it (the socket on the daystar card kinda sucks)
  4. when you put it back in the IIci did you get a sad mac code?
  5. just confirming, that, yes, it was a bad cpu. I put a coldpack on the cpu for 10 minutes and it booted right up, swapping the cpu with another mac completely fixed the problem.
  6. I spent some more time on this and I'm starting to suspect a bad CPU. I put a cold pack on the logic board and set it on the cpu for about 10 minutes. Then I put the board in the machine and tried it again. This time it booted, but within a minute or so of reaching the desktop It bombed with an illegal instruction. Any thoughts on ways to confirm this without buying a CPU? I don't want to waste any more money than I absolutely have to.
  7. I'm trying to fix my LC 575 sad mac. It was working up until a point last year, when it started to sad mac at random. At which point I realized that the caps had leaked. I proceeded to wash the logic board and recap with tantalum capacitors. Unfortunately the sad mac faces continued. I've washed the board several times to try and rule out cap juice. They symptoms went from being slightly random to very consistent. I've removed the hard drive and I've only got a cd-rom installed. I've also removed the battery. Here are the sympt
  8. Pushed an update to github, I've also updated my write up. http://andrew.colchagoff.com/netscape/part2.html would anyone have an interest in a live stream if I set one up of my next coding session? I'm thinking of pickup a device to capture the screen on my g3 and stream i with a mic of my talking, but it might just be a little bit to dry....
  9. i've added .sit files to the repository for everything just in case but the source files shouldn't have resource forks. My understanding of binhex is that its purpose is to avoid data corruption when a file is moved by an ascii only server which github is not. Do you think binhexing is necessary?
  10. Okay I've got my first dev build and the source on github. (After all that I used a zipdisk to move the files to my modern mac and commit) https://github.com/denodster/mozz I've compressed anything that I know to have a resource fork in a sit file but I may have missed a few things... it appears github doesn't know anything about mac linebreaks.
  11. great find, I've got one of these with a 500mhz g4 upgrade from powerlogix, I do all of my retro dev work on it. having both IDE and SCSI is nice because I can put a large hard drive in it without needing to search too hard, and I can still hook up all of my scsi stuff as well.
  12. Also, what is your preferred way to getting code from your mac to github?
  13. This project uses of Open Transport 1.1. I'm currently successfully building the PPC version on OS 8.1 and I'm slowly working my way through the libraries trying to compile 68k versions. Codewarrior Pro 2 has 68k equivalents of nearly everything necessary. but the answer may be to steal the TLS from Classilla if I can get the 68k version to compile. That being said I expect if I can get the project to build on 68k I might be able to attract some other devs. so who knows where it would go after that. After surfing the net with it on my G3 for a little while I woul
  14. I found it around the same time actually, and it did everything I hoped it would do. I needed to solve one more problem, but I successfully built the project. I turns out I also needed to be running an HFS file system and Mac OS 8.
  15. Sooo quick update, but 6 months later and I've successfully built the source. It was a beast to get it to build as I discovered that it only builds in Codewarrior 2 Pro and on top of that only builds in Mac OS 8 on an HFS filesystem. I consider all of these things good signs as I believe this means the end product will run in system 7.6 Now on to the next step which is going to be trimming the fat. I only want navigator, so Ill be cutting the composer and the other extra parts of the mozilla suite. From there I'll try to clean up some of the multi platform code, as it is pointless for building
  16. I think it might work better in my mozilla build efforts. but it's not on the Macintosh Garden, ebay, or anywhere else that I've looked.
  17. So I'm going to attempt to build the March 31st 1998 version of mozilla for PPC using sheephsaver on my Macbook pro. The plan is thus: Build for PPC Remove as as much code as possible (Composer, mail, other unnecessary portions of the mozilla suite that I don't care about) Swap libraries and build for 68k make https work for the enjoyment of secured crappy html web fans everywhere... or maybe just people who want to post to 68kmla on their vintage macs... Is this worth my time? probably not, but I'm also a web developer and have been itching to get a better understanding of the core wor
  18. dude thanks, thats exactly what I needed (believe it or not the built version was there too)
  19. Personally I'm fine with the whole crappy html only experience I get in Netscape 4, I just would like to be able to load sites that are now https only such as 68kmla I think our machines could handle https if there were a 68k browser out there that knew how to do it on the modern web.
  20. I think given the forum's use of https it would be very difficult. system 7 today used to run a forum that was written witht he explicit purpose of working on system 7 machines, but he shut that down as it was becoming too difficult for him to maintain http://forums.system7today.com/
  21. I'm currently working on building the first release of Mozilla for PPC mac. based on what I'm looking at it had a build target of a PPC mac running MacOS 7.6. the 68k c++ seems to be present in the source as the maintainers were asking for someone to devise a 68k build of Mozilla, but no one ever stepped up. My thinking is that if I can get it to build on a PPC mac (In Sheephshaver) I can start to strip down features until I'm left with just a bare bones Browser. At which point I would try come up with a build process for 68k macs. From there we could implement modern ssl support if possible.
  22. Hey everyone, I've been on a search for a few days now for a particular developer tool that was once available for download from ftp.apple.com It's called ToolFrontEnd, It was a plugin that allowed developers to run MPW commands from codewarrior as part of their automated build scripts. Why do I need it? I'm trying to build the first release of Mozilla when it was first made open source in 1998. I've found an archive of the website for ToolFrontEnd on archive.org here: http://web.archive.org/web/19990909113056/http://developer.apple.com:80/dev/techsupport/develop/issue25/mpw.html
  23. I was talking about file timestamps specifically its impossible for a file created on a mac to have an actual creation date prior to 1984. If I have any scrap of success it's obviously going to be a hack and have downsides, so if someone is using an LC to keep track of an accounting ledger in the year 2040 they can weigh it as an option. I'm leaning away from moving the epoch, because it would cause a lot of problems with existing data. Instead, the idea is to repurpose dates between 1904 and 1984 to represent 2016 through 2096 since the calendars for said year ranges are the same. ob
  24. I'm sure that there will be some, however the amount of effort that is required to actually write a calendar routine with no bugs in it when apple supplied a perfectly good one in the macintosh toolbox on day one makes me wonder if there were really that many people who felt the need to reinvent that particular wheel. Choosing to repurpose a block of compatible dates from before 1984 would allow the apps that handle their own calendar to still have a correct month, day, and day of the week, while things that don't reinvent the wheel would display the correct year.
  25. Since my last post I've also put some thought into it, I hate the idea of screwing up the timestamps on everything so I was actually leaning toward reusing some of the dates prior to 1984 since it's impossible for any timestamps to actually occur before the mac itself. The Gregorian Calendar repeats itself every 28 years, so it might be easiest to simply set the clock back to the earliest compatible calendar year prior to 1984, and then hack the display routines to add however many years to the system year to make it display the current year whenever it encounters a date that occurs before
×
×
  • Create New...