Jump to content

9640News

+AtariAge Subscriber
  • Content Count

    2,479
  • Joined

  • Last visited

Posts posted by 9640News


  1. That should be fine. My phone timed out trying to download the file(s) which is not unusual as the coverage is not great right here. I should be able to get the files tonight when I get home.

     

    Beery


  2. I also could export as csv according to my export options in Outlook. Would you prefer .csv or .pst? Maybe I'll just send both.

     

    OK on both. Not sure how much embedded html may have existed back in that timeframe. Likely minimal if any which would make csv easy to handle. However, if there was an issue, the may be easier to work from the original with the PST.

     

    If the filesize does not exceed the upload requirements here, you could post the file(s) here if nobody minds.

    Beery

    • Like 1

  3. On the Geneve, all you need to do is get hold of the GenREF package. The PDF's are at http://9640news.ddns.net:8080/. That will give you the necessary information on how to use the LOAD command in the DSR XOP for MDOS.

     

    With the 7 byte header of the MSX file, I am not sure what the best way to deal with that may be. I'm guessing it may be simpler to load the image into CPU ram, then move the bytes into VRAM as that header will create an issue I do not think you can offset on the LOAD process to put it straight into VDP.

    One thing is missing if you want to display properly whatever is in VRAM. One will need to know what the VDP registers should be preset too for when the MSX VRAM dump was made. I do not know if there is a default setting common to all the MSX dumps, or if the 7 byte header someone eluded too contains information/references to the settings that should be used.

     

    Just so you do not get scared about the coding, MDOS code using the XOP's for a CPU to VDP transfer would involve some coding like the following:

     

    This is for assembly code:

     

    1. Reserve Program memory space (8K) plus 128K additional CPU ram via XOP (5 lines code).

    2. Get Pagetable (5 lines code)

    3. Call routine to set VDP registers (10 to 15 lines of code depending upon if Register content is in data/byte statements).

    4. Call DSR XOP referencing the PAB (3 lines code)

    5. Move CPU ram to VDP ram with CPU paging (10 or so lines of code).

    6. Observe display

    7. Scan keyboard for keypress using XOP ( 5 lines code) .

    8. Exit (BLWP @0).

     

    That is the simplest way with the PAB already defined with filename/location path. More bells and whistles like retrieving filename from command line or typing in a filename/path add more code.

     

    To do the same thing on a TI-99/4A or under GPL mode with a 9938/9958 would require a lot more code with respect to loading the file as you would probably do sector or record reads. It was always so much easier to do things for me under MDOS. It would probably be simpler in c99 or maybe even Forth. Maybe I have just given our Forth guru an opportunity for an app?????

     

    Beery

    • Like 1

  4. I also want anyone else to know that if they want copies of these message bases for a BBS they have or want to setup, I have no issue providing them a copy as well so we have multiple resources.

     

    Beery

    • Like 1

  5. I know someone else must have messages going back to 1996 from the Listserver (when it started), as there was an archive made by Mr.Moon around 2001 that went back that far. That archive has since disappeared. My e-mails start in August 1997 to the end of The River Listserver in on 12/31/99.

     

    I do need to understand things a bit here. Just to make sure I understand things here, this content is not included in the postings on the TI-99/4A group on Yahoogroups? If it is included in Yahoogroups, I already have it.

     

    If not, then I am thinking of the best way to get a dump of those messages. I think the easiest way if they are in Outlook, is to create a new "PST" file. Then highlight and copy the files, and paste them into the new PST file. Then, it would be just a matter of sending me the PST file. From there, I could then open it up in my Outlook, and write the necessary code to export those emails out as text files so they could be imported into a message base on my BBS

     

    You could then zip that file up, and either email it to me or upload it to my BBS at 9640news.ddns.net Port 9640.

     

    Beery


  6. Thanks for the link to the image. Are the "Ref" holes on the board for securing the Raspberry PI?

     

    One thing I saw was the orientation of the LED. Maybe I am missing something, but I would have thought you would have wanted to rotate the legs 90 degrees so they would bend in an L shape to face the LED panel without touching. Maybe you have something else in mind not obvious to me. Just thought I would comment.

     

    Beery

    • Like 1

  7. Hey,

     

    Hoping someone out there can help me. Google Groups has all the messages from comp.sys.ti online at https://groups.google.com/forum/#!forum/comp.sys.ti.

     

    One can go to https://groups.google.com/forum/#!searchin/comp.sys.ti/after$3A1986$2F06$2F10$20AND$20before$3A1986$2F12$2F31%7Csort:date and see the first message on the group where net.micro.ti was reborn as comp.sys.ti .

     

    Anyways, if someone with some web skills, there are some ways to crawl the usenet newsgroup. There is a utility at https://github.com/icy/google-group-crawler that I am not familiar with its use that may be able to grab those messages.

     

    If someone has the skillset to retrieve the messages, I would really like to preserve their content and put those messages into a database format for a BBS we can all read, etc.

     

    Minimally, if someone has the skillset, I would need the posts in some kind of database format with the following fields:

     

    Date:

    Subject:

    Author/Poster:

    Message content:

     

    From there, I can use my other Excel tools to process the database and export it into a common message base format.

     

    Anyways, I hope someone has the skills.

     

    Beery


  8. On the progress side, I was able to get the TIPI-PEB version working Friday, and then the last issue fixed today. There are 2 issues with the pcb design, both fairly easily worked around.

     

    Woot!

     

    [email protected]

     

     

    Great progress. Curiosity here with a question. Will the TIPI-PEB design allow the TIPI to be mounted on the card in the PEB, then it being just a matter to supply the extra cabling to the TIPI? I'm assuming this will take up 2 (3??) slots due to the extra width if you are going that route?

     

     

    Beery

     

    Beery


  9. OT: Why do I frequently see a broken image link for your avatar? (The same happens with RXB.) When trying to display your avatar, I am directed to your F*book profile with an empty screen (lookaside...).

     

    I am blocking some FB links in my browser, but even when I turn it off it does not help. At other times I can see your profile pic again. Maybe it would be better to upload a separate image to AtariAge without linking to FB.

     

    First time I have seen the broken link. I did upload an image to resolve the issue.

     

    Thanks for the head's up.

    ​Beery


  10. Chris,

     

    I got time today to pull the old Geneve monitor out and replace it with a 21" widescreen today using the two cables mentioned and the SCART to HDMI converter I referenced in another thread. All looks and works well.

     

    Would love it if someone produces a 3D case for the card!!! Hint hint for someone!

     

    Anyways, all is well, and the image quality looks great. I have not attached speakers yet which will be the next step when I get time.

    ​Beery

    • Like 2

  11. I got this feedback regarding the DREM-2.

     

    > Will the unit support both floppies and hard drives simultaneously

    > with DREM-2? With DREM-1, it was either floppies or hard drives, but

    > not both from the specifications I read. I did not know if you were

    > making the unit more compact with a single board, or if there would be

    > more features in the redesign.

     

    Correct. Initial release of the software will be the same feature-wise.

    Butt with future software update DREM-2 will do FDD & HDD simultaneously.

    Board itself now fit standard 3in drive bay and most FDD chaises.

     

    DREM has 1Mb of RAM and 9K FPGA, DREM-2 has 128Mb jf RAM and 25k FPGA

     

    which will give us a room for improvements.

    DREM-2 has RTC (on DREM КЕС is not available for FPGA) now all files on SD card have proper data & time stamps.

     

    There is 90 degree 2 color SMD LED's on DREM-2 front edge, displaying HDD/FDD/SD status access/write

     

    > On another question, I currently have a Lotharek floppy emulator (see

    > http://hxc2001.free.fr/floppy_drive_emulator/index.html#FILESSUPPORTED

    > ) for one of my computers. I use the HFE image format with my

    > existing controller. Will your floppy emulation be compatible with

    > that format? If so, that would be great.

     

    DREM is using plain DSK images. You may convert your hfe's to dsk in batch mode.

    • Like 1

  12. I've been continuing to follow the progress of this device that replaced a MFM hard drive. There will be a new revision of the board, and from looking at the photos, it looks like it will have both floppy connectors and hard drive connectors all on the board. Whether they both can be used simultaneously, I am not sure. His last production run, the company screwed up and put the chips in the wrong place. This newer run will be out somewhere in a month or so.

     

    I do have a question for those familiar with the intricacies of hard drive formats, etc. The website for Revision 1 list the following details on supported formats listed below. The Myarc HFDC format for hard drives is covered, right? I just want to make sure nobody sees something obviously an issue or lacking before I become the guinnea pig.

     

    Thanks.

     

     

    Low level formats supported:

    • DEC Pro-350 RD, Elektronika MC-0585 (aka Elektronika 85) RD, DVK DW

    • DEC RQDX3

    • Adaptec ACB-4000 (E-Mu Emulator II+HD)

    • Seagate ST11 / ST11R

    • Western Digital WD1010 based controllers (any sector size, CRC16)

    • Western Digital WD2010 based controllers (any sector size, CRC16 and ECC32)

    • Western Digital WD5010 based controllers (any sector size, CRC16 and ECC32)

    • Western Digital WD5011 based controllers (any sector size, CRC16 and ECC32, ECC56 RLL)

    • Western Digital WD50C12 based controllers (any sector size, CRC16 and ECC32, ECC56 RLL)

    • Intel P8206 based controllers (WD2010 compatible)

    • DTC WD1010 compatible controllers

    • DTC WD2010 compatible controllers (i.e. DTC-7180)

    • IBM 1501492 (XEBEC)

    • Like 1

  13.  

    Source is available to the HFDC eprom though it might be version 12 which introduced a bug in some of the cluster calculations. That wouldn't matter for your formatting endeavor and I believe the format code is relatively self contained.

     

    Is the source on whtech? I looked a week or so ago, and did not see it.

    Beery


  14. As a DS/DD diskette. The Kyroflux details Jon posted are from my diskette. I'm wondering if what Michael learned about the mixup in bits is potentially the cause for the Lotharek image not being able to be formatted. Or, if there was something else at issue.

    Beery


  15. OK, after all this. Does any of the information learned explain why a Myarc HFDC can not format successfully a Hxc Lotharek DS/DD disk image?

     

    Did the Myarc Eprom DSR have a bug that impacts formatting an image file?

     

    On the last note, did anyone ever have the source code for the Myarc HFDC eprom? I know we have the source for MDM5, but what about the source for the eprom?

    Beery

×
×
  • Create New...