stardot.org.uk

C99 and C++17 both support hexadecimal floating point constants so it should be possible to exactly represent the beeb's 40-bit constants. Somehow I'd got the idea that early BBC Basic versions used the ratio of two polynomials, but that seems not to be the case. You were right. The beeb uses contin...

Unless there's some other code you're not posting which makes the css rule domain specific, adding things like that seem like a very bad idea to me. I would recommend using an element blocker like ublock origin for things like that. I like living dangerously! But it's a fair point. Here's a ublock ...

danielj wrote: ↑

Sun Jun 17, 2018 6:32 pm

can the same be done in Chrome?

I don't use Chrome but a quick Google search suggests they removed the built-in feature. Apparently you can get add-ons for Chrome that let you do this.

Edit: there's a safer method below. You can hide these messages locally by adding .notice {display:none} to your browser's user-defined css. In Firefox this is in the file: C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\Profiles\<profile>\chrome\userContent.css You could use greasemonkey to do some...

Yes, that's right. I find it helpful to remember that the value at the top of the stack is always at &101+S (ignoring when S=&FF). I guess the original return address is still sitting there at &10B/C+X, and would need to be removed at some stage. At the start of .code2 it gets overwritten by the new...

.code1 LDX #&07 .loop1 LDA &00A8,X ; Copy 8 values from &AF-&A8 to the stack. PHA DEX BPL loop1 PHA ; Create space on the stack PHA ; for a return address. TSX LDA &010B,X ; Copy the original return address STA &0101,X ; into the space just created. LDA &010C,X STA &0102,X RTS ; Return to the calle...

I used a similar build system for my sideways ROM projects bitd. I had a Watford board, which works as you describe.

They build fine using beebem and the code ends up in RAM bank 4.

I can't see the image either, whether logged in or out. If I use wget I get a straight 404 not found. Is it expecting a cookie to say you've accepted cookies? I've somehow avoided accepting the cookie permission thing. Edit: This is unlikely to be the problem. Other images work OK. It's just this one.

Whilst I'm on the subject of images - we allow linking to images in signatures - this breaks the ssl thing a bit, as external images might not be over secure links. I can turn this off, but it'd mean no images in sigs... Thoughts on that? Inline images have the same issue. This page shows an exclam...

* Information (including any program content) posted on a forum is considered to be in the public domain, GDPR does not superceded a persons responsibility to protect their own information, or be accountable for what they disclose in public. In such cases existing laws still apply. I think it's wor...

Comparing it to frogger you've changed the horizontal sync width from 8 to 9 (R3 from &28 to &29). Is that a typo?

No, thank you! That's brilliant. I've committed a new Windows exe. We might as well carry on in proposed-updates, it's easier to type and you've tagged the release if anyone wants to go back to that particular version. Though I committed the exe to master so that would have to be merged back in to p...

On a real beeb keywords like COLOUR and PRINT are tokenised to a single byte when you enter a line of code, so abbreviating them doesn't make any difference to the memory used.

You could possibly shorten this by using a four-element array for the positions and a similar array for the velocities. 0REM Walking Lines 10MODE2 20VDU23,1,0;0;0;0; 30X%=640:Y%=512:A%=768:B%=768 40V%=32:W%=24:C%=16:D%=-28 50DIME%(7),F%(7),G%(7),H%(7) 60FORI%=1TO7 70GCOL3,I% 80MOVEE%(I%),F%(I%):DRAW...

Bravo!

This is brilliant. The graphics look incredible, the animation is absolutely rock solid and the sound works really well. And it's a good game!

Prime wrote:Also what is the currently worked upon branch of the source as I'd like to test the updates.....

https://github.com/stardot/beebasm/tree ... ed-updates

Note that the EXE isn't quite up-to-date. It does include all the new features.

I'm loving these animations.

Having already written some code to convert the original pictures into MODE 2 format I extended it to handle the animations. A couple of ssds are attached.

I have had a look at rewriting the code to avoid the warnings by using ostringstream, which we already used in other places, so there's no new compatibility problem this way. This builds fine on Windows. The boot functionality works. I also tested a couple of the BASIC error messages and the rest l...

I merged my change. Yours looks good too.

I'm open to suggestions, but we could just #define (or 'const double our_pi = ...') our own constant here, if trying to use a library-provided value is causing problems. I can't see PI changing in the near future or across platforms. :-) I was thinking #undef/#define M_PI but you're right, a new co...

With gcc, M_PI seems to come from the platform math.h (via cmath), which on openbsd contains: #define M_PI ((double)3.14159265358979323846) /* pi */ Which is an old-style cast, hence the error. M_PI doesn't seem to come from any standard, so it's hard to say this is wrong, but the type of a real con...

Thank you Steve and Kieran, I can push to github now.

There's a new exe on github. The last commit is a fix to the buffer overflow identified by tricky in the previous post.

Please give me (mungre) permission to commit to beebasm. Thanks again.

Edit: To add some context, I asked SteveF who's currently maintaining beebasm but he's not an admin so he directed me here. I think what I'm actually asking for is to be added as a collaborator to beebasm.

For me, a single mention of my stardot username in the credits file is enough. More detail is available in the commit log. You could maybe change the copyright to something like "Copyright (C) Rich Talbot-Watkins and the contributors 2007 - 2018". I have updated the Visual Studio project files (to a...

As far as I can see fsd2fdi doesn't handle the complex cases of overlapping sector reads and the like. And it will never handle weak bits so a few games simply won't work with this approach. So there seem to be two options: * Create yet another file format that does handle weak bits. * Support fsd. ...

In terms of what's practical for emulators, we know from Pernod earlier that MAME needs something it can turn into an MFM bit stream. So ambiguity on overlapping sectors is problematic. Yes, it's a problem, but it's exactly the problem we've got. How to handle the existing fsd files. As above, in m...

This is really nice. I drank a coffee and watched it as a break from thinking about beebem and disk emulation!

One of the non-obvious parts of fsd is the handling of over-read sectors. For example, when the error code is &E1 the data includes the current sector, its CRC, the gap, the next id field, another gap and a chunk of the next data field. And, most importantly, any additional data stuffed in between t...

Sorry, I wasn't very clear. This isn't something new. I'm attempting to document the format of the hundreds of FSDs that already exist.

I get the impression that the design was largely driven by ease of acquisition.

Updated documentation for the FSD format based on sweh's original, discussions with billcarr2005 and looking at the files. Header: ======= Identifier: "FSD" string literal 3 bytes Creator: 5 bytes; date of creation/author Title: Character string (unlimited length; may contain any but null) Title_End...