RE: MasterBasic PDF Version 1 [ now ready ]
I can only see the English version... ;) G From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]Sent: 12 December 2004 14:51To: sam-users@nvg.ntnu.noSubject: MasterBasic PDF Version 1 [ now ready ] Hi Folks, Just had time to finnish this, and its ready for download from the Pro-Dos site. http://www.samcoupe-pro-dos.co.uk/sammanual.html [ now looking off a Sam pfd project , what would you like? ] Regards Steve(spt) __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Re: MasterBasic PDF Version 1 [ now ready ]
From: [EMAIL PROTECTED] Just had time to finnish this, and its ready for download from the Pro-Dos site. Excellent Job ! That also counts for the Masterdos update. However I wonder. Does the masterbasic manual realy start out with contentEs on the first page ? Edwin
Re: MasterBasic PDF Version 1 [ now ready ]
Quoting [EMAIL PROTECTED]: [ now looking off a Sam pfd project , what would you like? ] Do you have the wee manual that came with Nev's IDE interface? Colin, do you still have the software? (Nev has given us permission for both) Cheers, Gavin
Re: MasterBasic PDF Version 1 [ now ready ]
Gavin Smith wrote: Do you have the wee manual that came with Nev's IDE interface? Colin, do you still have the software? (Nev has given us permission for both) Yeap... i've still got both the manual and disk from the interface. Colin. = *** Dec 2004 sees Sam's 15th Birthday - Special offers on website! *** *** Third offer currently open - 10% off PC Keyboard Interface *** Quazar : Hardware, Software, Spares and Repairs for the Sam Coupe Website: http://www.quazar.clara.net/sam/ and http://www.samcoupe.com/
A Comprehensive List
Just a thought - does anyone have a comprehensive list of software that was release on the SAM? A complete list of commercially released games and a utilities, a list of magazines that were available etc. On the new site it would be nice if each bit of software could be accompanied by screenshots and reviews from the magazines, or links to places like YS Rock n Roll Years with the SAM reviews on. Is compiling a comprehensive list something that we should be looking into doing, so that we know what we're going to try and ask permission for, or is there one already available. Just a thought. J
Re: A Comprehensive List
Quoting Johnna [EMAIL PROTECTED]: Just a thought - does anyone have a comprehensive list of software that was release on the SAM? A complete list of commercially released games and a utilities, a list of magazines that were available etc. On the new site it would be nice if each bit of software could be accompanied by screenshots and reviews from the magazines, or links to places like YS Rock n Roll Years with the SAM reviews on. That's exactly what will be on it, for all titles, even if we aren't allowed to distribute the actual software. Is compiling a comprehensive list something that we should be looking into doing, so that we know what we're going to try and ask permission for, or is there one already available. I was hoping we'd have a wiki page up by now that people could add to as titles came to mind but the webhosts are having problems with the server that we are using (called Banana) - it took over 24 hours to upload the SAM User Guide for example - so it's all rather painful at the moment. They've promised a resolution some time today and then things will move quicker. Gavin
MasterBasic Manual Errors Do you know any?
Hello folks, MasterBasic pdf version 1 is 50% complete – all text has now been OCRd . Before I format the word doc , I want to ask you the following;- Q 1 . Would you like any errors in the manual fixed where they appear? yes/no Q 2. Any errors in the manual to be included as a page at the end of the pdf? Yes/no Q 3.Do not include anything keep it as the original Yes/no Q 4. Do you know of any errors? Known errors Page 16 “Join To a$ to a$” should be “Join To a$ to b$” page 49 “POKE XVAR 8,4” should be “POKE XVAR 8,20” Page 51 “Normally 4 (bytes in sequence),27,82,2,35,0,0,0” should be “Normally (bytes in sequence) 4,27,82,2,35,0,0,0” Regards, Steve(spt) morrgancp at aol dot com
RE: Format returns
[EMAIL PROTECTED] wrote: Yer - I was asking about this - If needed I could contact bob as I have several old format issues I could turn into pdf. I have the full set in my attic. Probably being eaten by spiders we you read. Nev
RE: Porting SimCoupe to RISC OS
Tarquin Mills wrote: When I tried compiling SimCoupe on RISC OS (the SDL version) I got the following output:- I'll reply to this off the list, for the sanity of other list users... :-) Si
RE: SDI a nef diskimage format ?
Andy Chandler wrote: will cope with all but one SAM disk I've seen so far :-) I'm betting that was another Mr Owen creation ;-) It's actually Chris Pile's original Defender disk, which does some gap-level checking as part of the copy protection. The gap information isn't stored as part of the disk image, as it's almost never needed, and would more than double the image size. SimCoupe actually fakes the raw track data from information it knows about the sectors on the current track, so it looks pretty authentic in programs like SAM DICE. Using a tagged disk format it would be possible to include a READ_TRACK dump for just the one track needed, to hold the information Defender expects. Due to the controller bug, it wouldn't be easy to write back to a real disk using a generic image writer (unless another tag held formatting hints!). The track data would also be enough for SimCoupe to run the protected Defender image too, which would be an added bonus ;-) Si
RE: SDI a nef diskimage format ?
Hi, is there a format for SimCoupe similar to Sinclair Spectrum Z80/Sna format ? Regards, Dumitru Florin Gabriel ( Zecut0r ).
RE: SDI a nef diskimage format ?
Nev Young wrote: why not create an image that is a full track image from index hole to index hole including all the inter sector guff. That should cover just about everything. It would indeed, if there was a reliable way to dump them! You'd really need all the sync marks as well as the raw track data, but even reading the raw track data is a problem... Unfortunately, the WD1772-02 controller leaves the address mark detector enabled during the diagnostic tracks reads, meaning certain patterns in the data can cause a false sync. If this happens the controller returns MFM bits instead of data bits from that point on in the track, making what you read essentially useless. I tried this method when writing the original MakeSDF scanner, before spotting the problem and working out what the heck it was doing. The PC controller allows you to read ID field headers and data, but doesn't give access to anything in the gap areas. There is a Disk2FDI program that can do it, but is a commercial program and requires 2 floppy drives. It spins both drives up and starts the read of a high-density disk in drive 1, then switches the drive-select to drive 2, with the controller then returning MFM _and_ data bits for the disk in drive 2. Very clever, but it's DOS-only and wasn't particularly reliable when I tried it a while ago. Another option is to use a Catweasel controller card, which can read just about any disk at very low level. They're not cheap though, and it's not really something most people will have access to for dumping. For now the header/sector-level scanning seems to be about the best solution, and will cope with all but one SAM disk I've seen so far :-) Si
Porting SimCoupe to RISC OS
When I tried compiling SimCoupe on RISC OS (the SDL version) I got the following output:- *make g++ -O2 -D__STRICT_ANSI__ -ISDL: -Izlib: -I. -I../Base -I../Extern -DUSE_ZLI B -Wall -c -o ../Base/ATA.o ../Base/ATA.cc In file included from ../Base/ATA.cc:23: ../Base/ATA.h:55: warning: ignoring #pragma pack ../Base/ATA.h:105: warning: ignoring #pragma pack In file included from ../Base/ATA.cc:25: ../Base/Frame.h: In member function `void CFrame::SetMode(BYTE)': ../Base/Frame.h:97: warning: sorry: semantics of inline function static data `void (CFrame::*apfnLineUpdates[4])(int, int, int)' are wrong (you'll wind up with multiple copies) ../Base/Frame.h:97: warning: you can work around this by removing the initi alizer ../Base/Frame.h: In member function `void CFrameXx1fHiRes_::Mode1Line(int, int, int)': ../Base/Frame.h:238: error: `g_fFlashPhase' undeclared (first use this functi on) ../Base/Frame.h:238: error: (Each undeclared identifier is reported only once for each function it appears in.) ../Base/Frame.h: In member function `void CFrameXx1fHiRes_::Mode2Line(int, int, int)': ../Base/Frame.h:299: error: `g_fFlashPhase' undeclared (first use this functi on) make: *** [../Base/ATA.o] Error 1 * -- Tarquin Mills (Chairman) ACCUS (Anglia Classic Computer Users Society) http://www.speccyverse.me.uk/comp/accus/
RE: Dial 0898 299 380 through time
Edwin Blink wrote: BTW I've also found a SAM Newsletter with the stuff. Anyone remeber those ? Yeah, think I've got them all in a folder somewhere, along with the newsletters from Enigma's Sam Software Club. G __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Re[2]: SDI a nef diskimage format ?
On a side track (hah), has anyone else found that all their old Sam disks are completely unreadable? Is it likely that I had a drive that, while being in-spec of the other Sam drives, is out of spec enough so that the average PC drive can't read floppies created by it? Or is it more likely that almost every single one of my disks have simply degraded over time? I've found that all my bought Disks seem to have faired very well and were still readable. Some of my blank disks I had written files on, were sometimes readable in drive 1 or sometimes in drive 2, but then my two drives always seemed to be a opposite ends of calibration to each other.
MasterDos Manual pdf Version 1
Hi folks I had 10 mins spare today so here is MasterDos manual pfd version 1. Now , my Masterdos disk was version 2.1, then updated on 6/6/92 to version 2.3. if there is any thing different in the manuals from version to version then let me know, and I will compile a new pdf. Its on the Pro-dos site:- http://www.samcoupe-pro-dos.co.uk/sammanual.html [ next pdf Project MasterBasic ] regards Steve (spt)
Re: SDI a nef diskimage format ?
Geoff Winkless wrote: On a side track (hah), has anyone else found that all their old Sam disks are completely unreadable? None comepletly unreadable, many with errors which ment I couldn't make a DSK of them at the time. Unless SamDisk2 can skip errors (I haven't got the URL to hand) they will have to stay in the old box for evermore :-( Dan.
Re: SDI a nef diskimage format ?
Simon Owen wrote: Does the archive need to be a single format for all disks? Or could the 95% of normal format disks be kept in a simple dumped image format, with only protected disks using a different format needed to describe them correctly? I think yes, the idea of tagging extra data into a header appeals but as Geoff pointed out we could have a standard header and then store the payload as a straight DSK or an SDF image (or SDF V1.1 with Freaky Cookie Malarky mode enabled). Dan.
MasterBasic PDF Version 1 [ now ready ]
Hi Folks, Just had time to finnish this, and its ready for download from the Pro-Dos site. http://www.samcoupe-pro-dos.co.uk/sammanual.html [ now looking off a Sam pfd project , what would you like? ] Regards Steve(spt)
Re: SDI a nef diskimage format ?
My two penneth of the disk format discussion: I like the idea of a new, all-encompassing disk format for the samcoupe.org archive (SCOA anyone?) as it will bring together many disparate formats DSK/SDF/SAD etc. into one, but it has to be able to hold the full geometry of the disk. After all, the idea is that the images in the archive should be true to the original format and IMHO there is no point implementing a new format if it cannot handle all disks, after all we might as well stick to DSK and SAD and the odd SDF for that. What we need to say is that this is the format for the archive and if anybody prefers to have it in DSK then they should be able to make it that way for their own needs, I am thinking of a parallel to getting a speccy .TAP file and converting it to a .Z80 because that's what you prefer to deal with but the .TAP file is the 'original format' that you take that from. Also, I think the idea of including data in the header of the format is vital - I have too may ARSE.DSK files knocking about and it will be a good method of preserving the information if authors, dates etc. in a standard and manageable way like it ID tags in MP3 files. In short: One site to store them all, One place to find them, One format to store them all and on the Internet bind them. :- Dan.
Re: Dial 0898 299 380 through time
Was wondering why a mail didn't got to the list Then I saw I mailed it to some one off-list. While I was looking for the masterdos manual, I found my correspondence with samco again including the letter that accompanied the hotline recording and was dated 10th January 1991. So I've updated the ID3 tags for the hotline recording with date and proper Colin. http://home.wanadoo.nl/edwin.blink/samcoupe/audio/hotline.mp3 BTW I've also found a SAM Newsletter with the stuff. Anyone remeber those ? Edwin
Re: MasterBasic PDF Version 1 [ now ready ]
opps --- sorry! and it was going so well ! "CONTENTS" Fixed ! Steve(spt)
Re: MasterDos Manual pdf Version 1
On 9 Dec 2004, at 5:21 pm, [EMAIL PROTECTED] wrote: Hi folks I had 10 mins spare today so here is MasterDos manual pfd version 1. Now , my Masterdos disk was version 2.1, then updated on 6/6/92 to version 2.3. Downloading it now - my had a blue cover, was that just a Format re-release thing? Gavin
Re: SDI a nef diskimage format ?
Simon: Good, bad or ugly? Sounds OK. Some things I thought up for 'PC' minded format: Have a format that consists only of track fragments (sectors). Each fragment had a 6 byte header folowed by at least 4 bytes data. So the smallest fragment was 10 bytes and largers 1024 (length/4-4 in one byte). Depending on the fragments type it contains all gap types, address marks, sector data. Besides the diskinfo there are types for file formats ID , end of image marker and discription. As with the other idea, only the used or required fragments are included and each of these track fragment could be anywhere in the image.(emulator should build a ordered offset table) Standard images can have just the sector fragments and protected disks can add extra fragments to rebuild a whole track. Ugly ? As for a encapsulating format: zip dsk,sad,sdf,fdi and rename the extension. Shoot me for this one ! Edwin
Re: MasterDos Manual pdf Version 1
I had 10 mins spare today so here is MasterDos manual pfd version 1. Now , my Masterdos disk was version 2.1, then updated on 6/6/92 to version 2.3. Gavin: my had a blue cover, I've got a 1990 First edition. It has a blue cover with a small window cut out where it read 'MasterDOS for the SAM COUPE user manual' IThe contents looks exactly the same as the PDF. The only difference is that mine came with snother a 4 paged photocopied set of masterdos hookcodes. Anyone have them too ? was that just a Format re-release thing? the scan on the last page of PDF says so. Edwin
Re: SDI a nef diskimage format ?
If one of you programming people need a Catweasel, I have a spare Catweasel MK3 lying around that I'd be happy to loan to you for the duration of this project if it does the community any good :-) Frans Simon Owen wrote: Nev Young wrote: why not create an image that is a full track image from index hole to index hole including all the inter sector guff. That should cover just about everything. It would indeed, if there was a reliable way to dump them! You'd really need all the sync marks as well as the raw track data, but even reading the raw track data is a problem... Unfortunately, the WD1772-02 controller leaves the address mark detector enabled during the diagnostic tracks reads, meaning certain patterns in the data can cause a false sync. If this happens the controller returns MFM bits instead of data bits from that point on in the track, making what you read essentially useless. I tried this method when writing the original MakeSDF scanner, before spotting the problem and working out what the heck it was doing. The PC controller allows you to read ID field headers and data, but doesn't give access to anything in the gap areas. There is a Disk2FDI program that can do it, but is a commercial program and requires 2 floppy drives. It spins both drives up and starts the read of a high-density disk in drive 1, then switches the drive-select to drive 2, with the controller then returning MFM _and_ data bits for the disk in drive 2. Very clever, but it's DOS-only and wasn't particularly reliable when I tried it a while ago. Another option is to use a Catweasel controller card, which can read just about any disk at very low level. They're not cheap though, and it's not really something most people will have access to for dumping. For now the header/sector-level scanning seems to be about the best solution, and will cope with all but one SAM disk I've seen so far :-) Si
