Quote from: Bryce on Yesterday at 19:52Slightly interesting, but absolutely nothing to do with CP/M. This is just to avoid security loopholes in script based languages / SQL code injection hacks. It has always existed, but the list seems to get longer with each Win version.Nah, it goes all the way back to DOS:
Bryce.
org #4000 ;de - loops
di
ld bc,&bc06
out (c),c
ld bc,&bd00+25
out (c),c
ld bc,&bc01
out (c),c
ld bc,&bd00
out (c),c
ld ix,0
xor a
or a ;C<-0
ld h,d
ld l,e
ld de,0
ld bc,1
.loop
add ix,bc
jr nc,loop
sbc hl,de
jr nc,loop
ld bc,&bc06
out (c),c
ld bc,&bd00+25
out (c),c
ld bc,&bc01
out (c),c
ld bc,&bd00+40
out (c),c
halt
ret
Quote from: HAL6128 on Yesterday at 14:49Is this from CP/M itself (until 2.2)?AUX: — an auxiliary device. In CP/M 1 and 2, PIP used PUN: (paper tape punch) and RDR: (paper tape reader) instead of AUX:
[/left]
LST: — list output device, usually the printer
PRN: — as LST:, but lines were numbered, tabs expanded and form feeds added every 60 lines
NUL: — null device, akin to /dev/null
EOF: — input device that produced end-of-file characters, ASCII 0x1A
INP: — custom input device, by default the same as EOF:
OUT: — custom output device, by default the same as NUL:
[/code]
Quote from: McArti0 on Yesterday at 12:41CRTC is not refreshing CPC only when R0=0. if R0<>0errata: CRTC is not refreshing CPC only when R1=0. if R1<>0
Quote from: Targhan on 23:50, 27 March 24What about something like LUA on CPC? It is simple, and can be added "modules" for more features, which could be added later.Sounds like a great idea!
Quote from: eto on Yesterday at 08:40Would an adaption of MMBasic make sense? It's designed for microcontrollers with limited RAM. Not sure if it's possible to adapt it for an 8bit processor though.The site states: "In its minimal version MMBasic typically compiles to about 94K of flash". Ouch!
Quote from: cwpab on Yesterday at 18:50Is there any possible explanation to why this happens in Windows 11, but not in Windows 10? (Maybe I should try creating a folder with those names from the CLI?)It does happen in all versions of Windows. I think the NT line always had ways of getting around it if you really wanted to create yourself headaches (using NTFS native paths for example) but Explorer always had a prompt to block you.
I mean, if they are supposedly "dragging" this from 35 years ago, shouldn't this also be an issue in ALL versions of Windows and not just in 11?
Page created in 0.050 seconds with 16 queries.