9640News

Posted February 8 · February 8

I have sent you a private note.

My BBS is not accessible after AT&T blocked my new service with a firewall that prohibits inbound connections.

Beery

February 7

8 minutes ago, Schmitzi said:

I press "F" here to boot from Floppydisk A: (720KB & MDOS 6.50)

I don´t know so I press "D"

Of course "N"ot

Welcome to MDOS 6.50 (where I cannot see the Flashdisk, no chance)

I think your comments indicate you did not update the PFM. Until you have fully understood the requirements, I would not do so as you would need to split MDOS first.

Also, you did right by selecting D for default.

Does this last picture indicated you booted from floppy and had MDOS 6.50? I do not see a prompt and wondering if you just took a picture before it was completed booting, or if there was another issue.

Beery

February 7

A Jumpboot disk can be created by formatting Interlace 1, Skew 2 on the floppy disk. Then, copying SYSTEM/SYS to it. If you want to use other files on that same floppy besides perhaps AUTOEXEC, then the disk needs to be formatted "normally", then reformatted "partially" (limited number of tracks, 1 side), so that SYSTEM/SYS occupies the interlace 1 portion of the tracks at interlace 1, skew 2 while the rest of the disk is interlace 3 or 4, skew 0 or 1(?). Not sure what the defaults were.

The challenge here is since the disk was formatted partially the second time, sector 0 and 1 is different than what it should be, so you will have to create a correct bitmap for sector 0 and 1 for the larger disk.

I hope that makes sense.

Beery

February 7

OK, here is Extended Basic and Editor Assembler, along with what I think was the general release for the PFM with some docs.

SCHMITZI.zip

February 7

3 hours ago, mizapf said:

Is there a way to split the loader on a non-PFM SCSI system? A short SCSI loader for DSK1, and the rest of GeneveOS on SCS1? Right now I'm booting by DSK1 only; this would certainly be helpful.

It would take a custom bios eprom to load a LOAD/SYS type file from DSK1 that would then load MDOS in its entirety from SCS1.

I have been working on an eprom version that would support TIPI/HFDC/IDE/SCSI/DSK, however I need to figure out why the HFDC/TIPI/DSK version did not work first. I will be posting code so if a person's specific needs aren't available, then they could tweak the code.

For some reason, I thought the Version 1.00 eprom supported the SCSI???? Maybe holding a key to pull the menu up?

Unfortunately, it does not appear Tony's code for the V1.00 eprom is available. And, for those that wonder, the display screen that replaces the swan, is actually a graphic, not "text" written to the screen.

Beery

February 7

1 hour ago, jedimatt42 said:

TIPI's TELNET is a proof of concept/example program so people can see what is possible with the TIPI TCP support... And a PI fixing tool in the event of desperation.

I don't BBS, so it isn't ever going to be a priority for me. But the source is available in the examples section of the github repo.

I've heard Beery has TCP enabled some other term program. Maybe it is more feature rich.

The 40 column version of MXT I was working from did not support ANSI. I believe it has log capture, but can't confirm with certainty as it has been over a year since I updated the program or looked at its features. MyTerm for the TIPI/Geneve setup does not have any logging capability as I disabled it due to ANSI as I have absolutely no idea how some of the log files would have even looked. I think @InsaneMultitasker had logging capability in PORT, but again, I do not know how that would look either on a printout with ANSI.

Beery

February 7

6 hours ago, Schmitzi said:

OK, a few ideas. Since you have had your HFDC in your system and it caused no harm, then I would suggest a couple of tests.

1. Set HFDC CRU to >1000 and install. yes, maybe I´ll get this done today

2. Boot MDOS using an AUTOEXEC that contains TIMODE if it is not already there.

3. Load GPL and Editor Assembler. What file do I take for loading the E/A ? Where from ? (Looking for XB too)

(I am sure I have all these files, I just don´t know which ones/which type...)

4. Go back to GPL screen (CTRL-SHIFT-SHIFT) and select Rompage mode.

5. Go into Editor/Assembler Option #5.

6. Load and run DU2K. Don't confuse with DM2K. oh yes, great idea, thx ! I used it a lot for checking DSR´s on the TI

7. Look to see what devices it detects. It should detect WDS1, etc. if it sees the HFDC DSR.

If it sees the HFDC DSR, then it is not totally bricked. If it doesn't see it at all, then you have definitely some significant issues. In this case, please post high quality photos and someone may be able to comment. This will bring the light

Take pictures of the pin settings on the Lotharek drive and post. Someone may be able to spot dipswitch issues. It has been a long time since I set mine up that is now not being used, but it seems there was either dipswitch settings or a config file that may need settings configured on either your USB or SD device. I may be wrong on this, but check. Maybe someone else can comment.

Oh yes, in all this fight with the controller and drives, I totally forgot about that.

BUS I configured the .CFG for 2 drives, some days ago: (See here, from my CFG-file):

The DIP-switches are set as follows: ID0A and ID2B are ON (now)

While on error (last drive = Lotharek #2) it was ID0A and ID3B set to ON

Sorry no pic because drives mounted this night But here a pic from the manuak, for better visualisation:

What kind of MFM drive are you wanting to use with the HFDC? Are you using a MFM drive, or the MFM emulator (DREM)? Or, no hard drive at all?

I am not sure at the moment, I have all type of drives and I have the DREM-Emu.

My latest idea was to use the HFDC for the big floppy drives and the new IDE for harddisk (we talked about before)

But I have no strict route, so please say me what is better)

Now, regarding the PFM. Is it the 384K or 512K version? Do you have instructions for using and installing MDOS onto the PFM? At this point, do not attempt to Save MDOS to the PFM as I think MDOS V5.0 and V6.5 are different size files, and if you have the 384K PFM, you can not install the complete version of MDOS on your setup. I have the 384K PFM myself and there are some things you have to be careful doing.

Yes it´s the 384K update "only", (and 192K video). (Can the 384K be updated to 512K ?)

And yes, I read your post here around talking about splitting the files (or so) so I already thought NOT to change anythng uih good luck

And no, I sadly have no instructions for the PFM handling but would love to have.

i.e. how can I copy a file/proggy to my E:-drive (which is small but very fast) ?

On copy, it does noot take any files.... I am sure this is part of the magic

AH OK, I have found the small PFM+ PDF file now 😍, I will study this soon.

But I miss some mentioned software like:

DISK2FILE & FLASHFIX

SCSISPLIT & SCSI4PFM (I can see SCSI4PFM in my AUTOEXEC, I think it comes from an older config)

and maybe more... (like LOADIMAGE for saveimage )

PFM+ instructions.pdf 155.35 kB · 1 download

BTW, what is the "File extension / F1 ... F10" thing ?

Beery

Thank you for support,

Ralf

SCSISPLIT breaks MDOS into two files. One is a 120K image, and the second is an 8K image (SCSI4PFM) that must then be loaded as a separate file from your AUTOEXEC.

The next revision of MDOS will have a TIPISPLIT that will break MDOS into three files. One file is a 120K image that fits into the PFM, and the second are 2 x 8K pages for the SCSI code and for the TIPI code.

DISK2FILE creates a “disk” image of files that are then written to the extra memory on the PFM where MDOS does not reside. That PFM disk can then be remapped for use, but it is write only. So, figure out what files you want (somewhere around 500 sectors) that can be searched using the PATH command that will make loading things easier.

I’m typing a bit remote, so ask later unless someone else responds with any PFM files. I’ve got them, but they are on the computer and I am on an iPad right now.

I will also try unless someone beats me to it, get the EA and Extended Basic files to you.

February 7

I have had to take a step backwards on the booting from a TIPI version of the boot eprom. It was working on my hardware, but not on a beta tester. When I started stripping hardware from my test system, I discovered it would not then boot.

Now, I have bracketed the non-working code, and I believe it is tied up in a DSRLNK call. Just need to understand what I need to do differently.

February 7

OK, a few ideas. Since you have had your HFDC in your system and it caused no harm, then I would suggest a couple of tests.

1. Set HFDC CRU to >1000 and install.

2. Boot MDOS using an AUTOEXEC that contains TIMODE if it is not already there.

3. Load GPL and Editor Assembler.

4. Go back to GPL screen (CTRL-SHIFT-SHIFT) and select Rompage mode.

5. Go into Editor/Assembler Option #5.

6. Load and run DU2K. Don't confuse with DM2K.

7. Look to see what devices it detects. It should detect WDS1, etc. if it sees the HFDC DSR.

If it sees the HFDC DSR, then it is not totally bricked. If it doesn't see it at all, then you have definitely some significant issues. In this case, please post high quality photos and someone may be able to comment.

Take pictures of the pin settings on the Lotharek drive and post. Someone may be able to spot dipswitch issues. It has been a long time since I set mine up that is now not being used, but it seems there was either dipswitch settings or a config file that may need settings configured on either your USB or SD device. I may be wrong on this, but check. Maybe someone else can comment.

What kind of MFM drive are you wanting to use with the HFDC? Are you using a MFM drive, or the MFM emulator (DREM)? Or, no hard drive at all?

Now, regarding the PFM. Is it the 384K or 512K version? Do you have instructions for using and installing MDOS onto the PFM? At this point, do not attempt to Save MDOS to the PFM as I think MDOS V5.0 and V6.5 are different size files, and if you have the 384K PFM, you can not install the complete version of MDOS on your setup. I have the 384K PFM myself and there are some things you have to be careful doing.

Beery

February 6

Zoom in 1 hour.

February 6

OK, a REMAP 5E command maps DSK5 to the Internal Geneve Ramdisk. It does NOT assign drive letter E: to DSK5. There are a list of A through Z drive assignments now with the upcoming MDOS release, but I think only A through S drive assignments are available to your MDOS.

If you are at the MDOS prompt, you should be able to do the following:

REMAP 1J

This should assign HFDC Floppy 1 to DSK1. HFDC Floppy in a Geneve system with two floppy controllers such as your setup, you must use the REMAP command to have access. In a single floppy control setup, the Geneve operating system will autodetect the HFDC and knows to use the HFDC for DSK1 through DSK4. So, if you have not used the ASSIGN command previously, you should be able to do either of the following:

DIR A:\

DIR DSK1.

You can also type the following:

ASSIGN <enter>

This will then give you a drive assignment list for all the current available drive letters. There is also a command LASTDRIVE that is a bit funny in its use if you want to expand drive letters (not DSK #'s) above I think it is drive J:\

There is also another command you need to use with a floppy only controller if you are using 80 tracks. Look at the SETDSK command.

Hope this helps you.

Beery

February 5

Thanks.

February 5

45 minutes ago, Schmitzi said:

Edit: The MaArc DDCC-1 is 80-track-modded, but I tried it in an easy configuration,

all 4 jumpers to off ( = 40 track) and only 1 drive, the Teac FD-55B.

But the same is on the Corcomp 9900 controller: If I do an DIR C : the only way out is powering the machine off

Review the REMAP command and make sure you are specifying the correct drives to the respective drive #'s.

Please specify what disk controllers you have and at which CRU's. The HFDC has dip switches on it that will identify the drive type you have connected. I think you also indicated you had a PFM, so please confirm as well.

By default, A:\, B:\, C:\, & D:\ default to DSK1, DSK2, DSK3, and DSK4. However, with two floppy controllers, floppy controllers will fill slots A:\ through D:\ requiring REMAP to access HFDC floppies. Then, you also need to Remap the PFM drive to a number which could be anywhere from 1 to 9. It is possible with REMAP to override floppy controller drives A:\ through D:\ if you so desire.

Now, I would then use the ASSIGN command to ASSIGN E=HDS1:, ASSIGN F=HDS2, etc. for the drive letters (not drive numbers) to individual drive letters. You can even use the ASSIGN command to ASSIGN E=DSK1: so that E: drive responds to DSK1, which could be a PFM flash drive that has been REMAP'ed to DSK1. Please note the ASSIGN command at the end of the statement ends in a colon, not a period.

The REMAP and ASSIGN commands are really versatile to your needs.

If you specify what devices you have and at what CRU's, we should be able to give you the commands to add to your AUTOEXEC file to get everything mapped to the way you want to access your system.

Beery

February 5

9 hours ago, GDMike said:

I'll probably use the tipi mouse if the Geneve gets to the point to start working with the tipi..

Or try to program the mouse, if it's possible in MDOS, or ...

It is possible to program the mouse from MDOS as I have some demo code that did not reach full functionality to do it using a new TIPI XOP. It is not ready to release and I have not visited the code since early last year. I will tell you at this point, it is easier to use the Geneve bus mouse for MDOS mode as everything is very well documented and there are plenty of examples.

I can tell you at this point in time, for you, if you wanted to use a Geneve mouse, the bus mouse route for a MDOS program would be simpler for you as the tools and example code is already out there for access. If you were to write your own MDOS TIPI mouse code, I can tell you that you are in for a challenge.

Now, if you were going to go the 4A route for programming, then Matt has a good information for accessing the TIPI mouse which gives you a good foundatioin.

Nothing says you can't have two mice on your system.

February 5

Rompage mode, which can only be "activated" while in GPL mode when you are emulating the TI-99/4A, maps out the Geneve master DSR so that you are actually using the DSR's on the cards instead. Thus, you can access TIPI and all its capabilities, accessing the Myarc HFDC results in using a device name of WDS instead of HDS, etc. There are some card DSR's that are NOT compatible with the Geneve, thus that is why the Geneve master DSR is the preferred route to go, and thus why there has been significant effort the past couple of months to add full TIPI functionality to the Geneve master DSR.

February 5

You have to be careful with the old Logitech bus mice. There were at least two variants, one was a high resolution and another was a lower resolution, and they had different pinouts. I believe it was Micropendium that had one article for a mouse, and I found out later the one I purchased was a higher resolution mouse. I finally worked out the pinouts, but it took time.

I've got Chris's USB mouse setup on my primary Geneve. I would go that route.

As has been mentioned in a few threads here on Atariage, there are not too many programs that utilize the mouse. MyArt is one for the Geneve, and I was just using it this past week. The Geometer's Apprentice and The Printer's Apprentice use it as well. Windows 9640 utilized it as well, however, I am not sure anyone is using that program, and I wrote it myself. I believe Stuart's web browser uses a mouse on the PI for the TIPI. So, I actually have two mice for my Geneve. One uses Chris's USB mouse, and the other a wireless mouse to the PI. I probably could have gotten away with a wireless mouse for the Geneve, but never tried it and don't know if Chris has any recommendations.

Beery

February 5

17 minutes ago, arcadeshopper said:

The Geneve mouse is the equivalent of the old logitech bus mouse

Shift 838 makes a nice ps2 to Geneve adapter

Sent from my LM-V600 using Tapatalk

Here's a Geneve manual with pictures.

MDOS Manualx.doc

February 4

The program that partitions the SCSI2SD runs under Windows and plugs into the SD card via the USB port.

You need to download the software from the SCSI2SD website.

February 4

The SCSI2SD has a program you run that partitions the SD card for you. Then, DU2K requires no parameters to be input to format.

52 minutes ago, dhe said:

My head hurts... Mizapf, would you mind doing a screen dump of your recommended parameters for DU2K?

I mean 124 MiB is still like a lot of 90K floppies! 😃

February 4

1 hour ago, arcadeshopper said:

Samsung 910mp

not mine just passing a deal along..this is the single best lcd for retro computing as it supports RF, Composite, svideo, vga and SCART rgb

It was sold.

February 4

Dan,

If you have DU2K that you can grab from Fred's website, that is the simplest tool. With SCSI2SD I setup 7 images at 256 MB. In just a couple of minutes, I formatted out all 7 images. I think @InsaneMultitasker indicated DU2K will only format up to 248 MB, so you may not get the full 256 MB.

I don't think one hits the limit with the SCSI2SD DU2K formatting issue, but there does become a point when MDOS when you do a DIR command can not display the actual number of free sectors properly. Even with the "large number" routine, when you get over a couple hundred million sectors free, the number is displayed incorrectly. Discovered that when "tricking" MDOS's reporting on sectors free with using the TIPI. Now, we just the setting of 9999 sectors free from the PI.CONFIG setting.

Beery

February 3

It's going to be a very long time before email is obsolete. Too many things rely on email until we get digital cybernetic implants that connect us into a network for communication. Not sure what one would then call a digital transmission to a cybernetic inbox when the user has a do-not-disturb flag or while they are sleeping. A good series of books to read is from Ian Douglas over his 20+ books gives a fictional account of our advancements in science that lead us to future exploration and discoveries.

February 3

Matt,

Nice addition and example you have for the PI.UDP capability. I had started looking at the protocols for POP3 and SMTP recently trying to understand what may be possible for some kind of simple email communication. I think your basic example would lend itself with the ability for an implementation possibly even within an extended basic program. Getting a list of emails on the server I think is viable, however, I start to struggle with managing the actual size of the emails as I am looking at one mailbox where most of the emails are 100K+ to MB in size.

Off the top of my head, I think this would really preclude any useful implementation. Even with a SAMS, I think this would be impractical. So, my question to you or others, does anyone concur with my reasoning or are there options I may not have considered?

I guess I could see the ability to send an email from one's TI, but it is the receipt of emails I think becomes the challenge unless I am missing something.

Any feedback is welcome.

Beery

January 31

If you have a zip drive hooked up and working on the Geneve, then just plug the unit in. Not sure how the device numbers will roll in the unit.

I have found DM2K, and I believe DU2K, both require to be run from Editor/Assembler, Option #5. On the Geneve, make sure you are in ROMPAGE mode.

Beery

January 31

The 6" or 9" cable is not really long enough for the PEBox, so get something a bit longer.

Beery

Sign In

Profiles

Member Map

Forums

Blogs

Gallery

Calendar

Store

Posts posted by 9640News