Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Apple II Pascal and harddisk support in emulators
535 views
Skip to first unread message
j.robert...@gmail.com
Jun 2, 2016, 2:23:16 AM6/2/16
to
I'm trying to setup a faster way to assemble code with the Apple Pascal environment. (for compiling Apple3 driver assembly code...)
I have found that Applewin runs quite fast for this when i set the emulation speed to fast as possible. Much much quicker than Mess running the Apple3 emulation.
The only issue with using Applewin is that I am limited in the size of files to the Apple floppy 140k limit, and 2 disks. I want to be able to create the code and listing with easy access via the disk images.
It seems that Apple II pascal 1.3 supports smartport type harddisks, but only when they are in slot 4,5, or 6.
Is there any other way to get Applewin running a harddisk on a different slot than 7?
/Rob
I have found that Applewin runs quite fast for this when i set the emulation speed to fast as possible. Much much quicker than Mess running the Apple3 emulation.
The only issue with using Applewin is that I am limited in the size of files to the Apple floppy 140k limit, and 2 disks. I want to be able to create the code and listing with easy access via the disk images.
It seems that Apple II pascal 1.3 supports smartport type harddisks, but only when they are in slot 4,5, or 6.
Is there any other way to get Applewin running a harddisk on a different slot than 7?
/Rob
mver...@libero.it
Jun 2, 2016, 4:35:40 AM6/2/16
to
No.
What you can do is create a Pascal partition on the (emulated) HD and continue to boot from slot #6.
The only reason I have to use KEGS & derivates is for the 3.5" disk in slot #5.
Marco.
What you can do is create a Pascal partition on the (emulated) HD and continue to boot from slot #6.
The only reason I have to use KEGS & derivates is for the 3.5" disk in slot #5.
Marco.
David Schmidt
Jun 2, 2016, 10:11:53 AM6/2/16
to
speed of iteration. I've even done virtual serial disks, sharing with
the /// so it can copy and boot with the new driver without having to
transmit a full disk image. When it comes time to lay down the bits for
a real release, I do the final assembly on the /// just for
authenticity's sake. Even though the binaries are identical. :-)
qkumba
Jun 2, 2016, 5:44:43 PM6/2/16
to
Did you know that you can hold the INSERT key to speed up the emulation in MAME (after pressing Scroll Lock to enable partial emulation)?
Depending on the activity at the time, it might outperform even AppleWin.
Depending on the activity at the time, it might outperform even AppleWin.
j.robert...@gmail.com
Jun 2, 2016, 8:36:08 PM6/2/16
to
On Friday, June 3, 2016 at 7:44:43 AM UTC+10, qkumba wrote:
> Did you know that you can hold the INSERT key to speed up the emulation in MAME (after pressing Scroll Lock to enable partial emulation)?
> Depending on the activity at the time, it might outperform even AppleWin.
Thanks, no, i had not realised this. I see that you can also specify -nothrottle to get max speed from the command line. It certainly helps the speed.
> Did you know that you can hold the INSERT key to speed up the emulation in MAME (after pressing Scroll Lock to enable partial emulation)?
> Depending on the activity at the time, it might outperform even AppleWin.
/Rob
j.robert...@gmail.com
Jun 2, 2016, 8:40:07 PM6/2/16
to
/Rob
j.robert...@gmail.com
Jun 2, 2016, 8:44:50 PM6/2/16
to
> I also do Apple /// Pascal development on a GS (GSport in my case) for
> speed of iteration. I've even done virtual serial disks, sharing with
> the /// so it can copy and boot with the new driver without having to
> transmit a full disk image. When it comes time to lay down the bits for
> a real release, I do the final assembly on the /// just for
> authenticity's sake. Even though the binaries are identical. :-)
Thanks.
> speed of iteration. I've even done virtual serial disks, sharing with
> the /// so it can copy and boot with the new driver without having to
> transmit a full disk image. When it comes time to lay down the bits for
> a real release, I do the final assembly on the /// just for
> authenticity's sake. Even though the binaries are identical. :-)
I have tried GSport now and it is working nicely. I can boot a pascal 800k image directly and have a second one for my work disk. Its also quite quick as well!
/Rob
Michael Pohoreski
Jun 6, 2016, 2:42:51 PM6/6/16
to
> Thanks, I could not seem to be able to get Applewin to not try to boot from the HD once i selected it in the config. Maybe i need to make a HD image without the boot sector?
Unfortunately that won't help. :-/
You'll manually boot slot 6 if you have a HD mounted. i.e. Press Ctrl-F2 (Reset), and PR#6.
I've logged two bugs/features for these issues:
https://github.com/AppleWin/AppleWin/issues/323
[ ] Can't skip HD boot
https://github.com/AppleWin/AppleWin/issues/324
[ ] Can't mount HDV in slot other then 7
j.robert...@gmail.com
Jun 6, 2016, 11:56:40 PM6/6/16
to
Ok, yes, that would work around it.
And thanks for adding these as a features/bugs to be added in the future.
/Rob
And thanks for adding these as a features/bugs to be added in the future.
/Rob
rho...@gmail.com
Oct 16, 2016, 6:25:47 AM10/16/16
to
Original author of the HD emulation here. Better late than never, eh?
I picked slot 7 for a few reasons, the first was that the other slots were already taken by useful devices. I also preferred the hard drive booting over the floppy drive, and as the IIe's boot code scans from slot 7 down to 1, slot 7 became the only viable choice for bootable Prodos volumes.
I think having it listen for a few thousand cycles for open-apple to be held down then divert to slot 6 is really the best, and, honestly, most accurate to historic hardware. There isn't much room left in the firmware image, but I think there might be just enough.
I picked slot 7 for a few reasons, the first was that the other slots were already taken by useful devices. I also preferred the hard drive booting over the floppy drive, and as the IIe's boot code scans from slot 7 down to 1, slot 7 became the only viable choice for bootable Prodos volumes.
I think having it listen for a few thousand cycles for open-apple to be held down then divert to slot 6 is really the best, and, honestly, most accurate to historic hardware. There isn't much room left in the firmware image, but I think there might be just enough.
A2CPM
Oct 17, 2016, 1:37:23 AM10/17/16
to
Hi!
On Thursday, June 2, 2016 at 2:23:16 AM UTC-4, j.robert...@gmail.com wrote:
> I'm trying to setup a faster way to assemble code with the Apple Pascal environment. (for compiling Apple3 driver assembly code...)
> I have found that Applewin runs quite fast for this when i set the emulation speed to fast as possible. Much much quicker than Mess running the Apple3 emulation.
> The only issue with using Applewin is that I am limited in the size of files to the Apple floppy 140k limit, and 2 disks. I want to be able to create the code and listing with easy access via the disk images.
<--- snip --->
See the topic "Rapid switching between the ProDOS and UCSD Pascal operating systems" in C.S.A2. The last message posted in that thread was on Aug. 11. The Pascal Partition Manager is a UCSD Pascal add-on that lets you store UCSD volume images at the end of a ProDOS partition. Maximum UCSD volume size is 16MB. So, you could have two UCSD volumes of about that size or you could have a boatload of images of UCSD 3.5 inch disks. Should be perfect for what you're trying to do.
Willi
On Thursday, June 2, 2016 at 2:23:16 AM UTC-4, j.robert...@gmail.com wrote:
> I'm trying to setup a faster way to assemble code with the Apple Pascal environment. (for compiling Apple3 driver assembly code...)
> I have found that Applewin runs quite fast for this when i set the emulation speed to fast as possible. Much much quicker than Mess running the Apple3 emulation.
> The only issue with using Applewin is that I am limited in the size of files to the Apple floppy 140k limit, and 2 disks. I want to be able to create the code and listing with easy access via the disk images.
See the topic "Rapid switching between the ProDOS and UCSD Pascal operating systems" in C.S.A2. The last message posted in that thread was on Aug. 11. The Pascal Partition Manager is a UCSD Pascal add-on that lets you store UCSD volume images at the end of a ProDOS partition. Maximum UCSD volume size is 16MB. So, you could have two UCSD volumes of about that size or you could have a boatload of images of UCSD 3.5 inch disks. Should be perfect for what you're trying to do.
Willi
0 new messages