I downloaded a number of BXY files (filename.bxy) that contained Christmas art for Apple II Programs. In the example below I used PublishIt4 to import the individual pictures.
Anyway, the bxy files contained 24 pictures each but only 8 can fit on a 5.25 disk image. Here is a picture in CiderPress. You can also create a .2mg file containing all 24 files if you want. I created all 24 on a 800k.po file and then converted it to the 2mg. Works perfectly fine in the Virtual II Emulator as long as you configure Virtual II with SCSI drives. See earlier blog post on doing this. I think you can search on OmniDisk.
I used File, Open dropdown to view contents. Then, I selected the pictures I wanted. Next, go to Actions, Convert to disk archive. Following usual CiderPress actions, Name the volume, click OK, and then save file, use same name or different name. This gives you a filename.po image which I loaded to my Virtual IIe Emulator. Below is a snapshot of PublishIt4 printout of some of the pictures.
Just installed my FASTChip //e In italics are the notes from the a2heaven.com website.
November 22, 2017
I’ve been running a tests of PublishIt v4 startup time on the Apple //e with the FastChip//e.
*With the FastChip//e set at 10 MHz and running PublishIt from the SCSI drive it took 8 seconds to load.
*With the FastChip//e running at 1.0 MHz running from the SCSI drive it took 25 seconds.
*With the FastChip//e running at 1.0 MHz and PublishIt v4 running from a UniDisk 3.5 disk connected the Liron Controller Card in the //e it took 53 seconds to load. [ Note: The Apple //e has a RamWorks8M card made from a2Heaven. This card uses current day technology so it must provide some additional advantage when loading the fonts, et al into memory upon startup. The only way to see the difference would be for me to uninstall the RamWorks8M and reinstall the 1986 RamWorks 1M card by Applied Engineering. At the end of this posts are links to YouTube videos of the above.
The FASTChip //e accelerates the Apple //e™ by replacing the on-board microprocessor with a much faster one. Because the memory on the Apple //e™ can only run at a 1 MHz speed maximum, faster memory (SRAM) must be provided to increase performance and allow the 65C02/65C816 CPU to run at full speed. To do this, the FASTChip //e contains 512KB/1024KB of fast SRAM memory. The clever design allows the acceleration of programs running in both main and auxiliary memory. The additional FASTChip //e memory can emulate both 192/448 KB fast RamWorks compatible RAM and 256/512 KB fast RamFactor (slinky) compatible RAM.
FASTChip //e features
- Easy to install card, installable in slot 1-7 of the Apple //e™, or Enhanced //e.
- Does not mechanically interfere with the 80 column card in slot 3.
- 65C02/65C816 microprocessor running at a clock rate of more than 16 MHz .
- External Hardware Control Panel with controls and LED display.
- CPU frequency can be changed real-time via rotary knob (0.2Mhz to 16.6Mhz).
- Stop/Pause and Status buttons for easy control.
- 4 digits x 7 segment LED display.
- Built in 192/448 KB fast RamWorks compatible RAM.
- Built in 256/512 KB fast RamFactor (Slinky) compatible RAM.
- Low power design for cool operation.
- Acceleration of programs running in both main and auxiliary memory.
- Compatible with most interface and expansion cards for the Apple II/IIe.
- Transparent operation with all Apple II software.
- An easily accessed built-in software control panel lets you control processor speed, memory, joystick, speaker sound quality and many other options.
My actual //e Setup with FastChip//e, RamWorks8M card and SDFloppy II installed.
FastChip//e videos of PublishIT version 4 at 10 Mhz. A program essentially unusable on a IIe at 1 MHz.
[Note: I’m running PublishIt from a SCSI drive, not a floppy, unidisk 3.5, or SDFloppy, although programs ran fine from all three devices. But obviously SCSI is the fastest ] : unless you have a CFFA or MicroDrive Turbo.
Updated March 15, 2018 Pi-Day
One Pi is font, the other image cut and paste from other document.
Updated March 12, 2018
More screen shots. Color and b&w pictures. [ Picture quality lacking as I got my iPhone to close to the LCD TV. I’m using the Scart Converter with special RGB Adapter cable. See other blog entry for details. ]
This picture is more representative.
Graphics I clipped from other programs using SHR screen capture NDA and then using SuperConvert4 or Platinum Paint 2 to clip.
October 15, 2017
UPDATE. I was running GW3 v1.1 in the previous examples. Below are the pictures of GW3 v2.0, which I added to the
GSHarddrive image today. GW3v2 is in a separate folder on the GSHarddrive. I updated the previous word processing file, which is illustrated.
This is a nice program for the IIGS. You can download this program from the link below. The download includes a number of files and versions of the program including some picture disks. You can also grab the manual which is very extensive. The program disks are 2mg files. The manual says you can load the program to the hard drive which I did and it works perfectly fine. I use it under a subdirectory GW3 on my main 32 MB hard drive. The program seems to come with the graphical and pseudo-graphical program features of this era. You have the font and formatting capabilities with multiple columns for text. and the ability to draw or have some type of image on the screen. A couple key things that I did, which I liked, was the ability to import AppleWorks files and also Bank Street Writer files. As you can see in the examples below I did both. [ I wonder if I ran the Spell Check in GW3. I’ll need to verify. ]
Import file options screen.
Below is a picture of the screen where I imported the AppleWorks file. This is actually the National AppleWorks User Group file that was on one of the disks I had. The funny thing that occurred is I enhanced the title of the page as you can see with the shadows around the letters but when you try to print that to a PDF out of the Sweet16 IIGS Emulator the shadow font does not translate and you get nothing but a big black space at the top of the very first page. I confirmed this by changing the font back to something more natural and it output the PDF just fine.
Here is a example of importing the Bank Street Writer Plus file from my disk. I try to keep mini-journals in all the different word processors I have, and their versions. This Bank Street Writer Plus file shows the embedded text formatting controls.
Here’s an example of importing one of the picture images that came on the disks with the program. As you can see I set the text to wrap around the image completely.
Lastly, here is a group shot of all four pages that printed including the header where I changed the font to not be shadow font, included the logo, the AppleWorks file, and the Bank Street Writer file.
Here is the MultiScribe program that became BeagleWrite. I didn’t have a MultiScribe Desk Accessory disk image so I just inserted the BeagleWrite Desk Accessory version and worked like a charm.
BeagleWrite was formerly MultiScribe. I’m giving this version 3.3 a try out. I downloaded the zip file (see link below) and started playing with it here in Virtual II Emulator. I tested the actual program disk, etc and then copied it to a subdirectory on the OmniDisk 32MB .2mg drive which I use as home base for many programs. [ note: I convert the .po files to .2mg and .do so they’ll run in the Emulator. I use the Wine version of CiderPress to do that on my MacBook ]. I have AppleWorks v2,3,4,5, PublishIt4, Copy II+ v9.1, Apple System Utilities 2.1 and 3 plus others (picture of them at bottom).
BeagleWrite ran fine from the OmniDisk “hard drive”. But I had to put the Accessories.dsk in the Floppy drive for them to work. I couldn’t find a option to change the path to the hard drive for them. Data disk path change was relatively straight forward. Enough here…more notes with the screen shots.
When spell checking it doesn’t give you intuitive corrections for misspelled words. Example: I spelled Spetember and it began making suggestions at “Sp”. Once you realize this things went very well. Nice Dictionary.
For some reason it starts the calendar at September 1918. You can quickly correct by grabbing the scroll down button.
This is before I added BeagleWrite and MultiScribe.