From: Cory Smelosky <b4 at gewt.net>
The disk is 1048778 blocks. I created a 512M image and copied it
bit-for-bit to the disk.
So you're saying the image *did* work under emulation and only broke when
you copied it to the first 512 MB of a disk that you then moved to a
controller with an unknown private partitioning scheme?
If I'm understanding you right then it sounds as if the controller may
indeed be storing its own stuff in the first block(s) and the partition for
DU1: isn't supposed to start until a few blocks into the drive. I would
experiment with that by zeroing the disk, and then partitioning it on the
PDP-11 (I assume this is done with the SCSI controller's firmware), move
it to the PC and pull off the first few blocks, then repeat the process
with different partitioning (assuming that's possible -- or do you mean
the firmware is hard-coded to split drives into chunks .LE. 512 MB?), and
see what changes in those first few blocks. It might be very obvious...
Another thing to do is generate a bunch of different boot blocks that look
like this:
.word 240 ;NOP (required by some boot PROMs)
.word 0 ;HALT (unless the PROM also requires a BR ...)
.word blkno ;block # you'll be writing this one to
.blkw 253. ;(junk for the rest of the block)
... and copy them to the first N blocks of the SCSI disk. Then when you
move it to the PDP-11 and boot from it, it'll halt, and if you examine the
word at 000004, you'll know which actual block was read in as block 0.
Then next time write your image starting at that block instead of 0,
and it might work.
If you wanted to get *really* fancy, maybe you could set up a Linux (etc.)
box as a SCSI target, and log the actual block #s accessed by the PDP-11?
Seems kind of ridiculous...
John Wilson
D Bit
On May 20, 2014, at 1:47 PM, Cory Smelosky <b4 at gewt.net> wrote:
Well, I'm just not having ANY luck with this...
...
SYSTEM CRASH AT LOCATION 014402
REGISTERS
R0=000002 R1=120550 R2=000000 R3=120546
R4=120744 R5=031610 SP=117772 PS=020010
...
I seem to be TERRIBLE and SYSGEN.
Maybe you just have a bad drive, and RSX is unhappy just as RSTS was.
paul
At 5:52 PM +0200 20/5/14, Johnny Billquist wrote:
Discontinued.
Of course... :-(
To new readers, let me introduce me.
I was the operator of nodes 10.1 (SHARK) and 10.2 (SNAKE) until I had to reorganize (== shrink) my server facility and flip the HECNET switch off on July 2010.
SHARK and SNAKE have resurrected from 4 years in limbo, thanks to VirtualBox. They are PDP's running 11M+. I even discovered a forgotten 10.3 (SQUID), with sysgened PC11 to spool data from/to Unix pipes.
That was the opportunity to check HECNET community health, and I am pleased to see it is in great form. This list is one of the more active I subscribe to. I was surprised to see 10.1 and 10.2 in MADAME's nodes table. Is this for real? I thought they had been purged or reassigned for long.
Virtualization had the side effect to move simh from Mac OS X to Linux, and things are much more simpler and up-to-date (Apple don't care BSD besides its own needs).
I am now trying to install DECNET for Linux. This will allow to move large sound files from the ancient world to the present.
--
Jean-Yves Bernier
Well, I'm just not having ANY luck with this...
VMR @SYSVMR
VMR -- *DIAG*-Partition reduced to executive common size
INS EXCOM1
VMR -- *DIAG*-Partition reduced to executive common size
INS EXCOM2
VMR -- *DIAG*-Loadable driver larger than 4K
LOA TT:
VMR -- *DIAG*-Installed tasks may no longer fit in partition
SET /TOP=DRVPAR:-*
POOL=1200:9644.:09644.
(That bit is understandable. I must've configured it too big!)
boo [1,54]rsx11m
SYSTEM CRASH AT LOCATION 014402
REGISTERS
R0=000002 R1=120550 R2=000000 R3=120546
R4=120744 R5=031610 SP=117772 PS=020010
SYSTEM STACK DUMP
LOCATION CONTENTS
117772 000004
001344
After reboot:
boo [1.54]rsx11m
MCR -- Task not in system
ins $boo
boo [1,54]rsx11,\,\m
[no output]
I seem to be TERRIBLE and SYSGEN.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
The item shown is just the interface box. The Pro 300 series Technical Manual describes the whole system it consists of three parts, the one shown in the Ebay entry is one of the three the Voice unit , which is basically a speakerphone box with some extra buttons on it that the software can see. Not clear if the other two parts, which are the important ones, are included in the offer.
paul
On May 20, 2014, at 1:04 PM, lee.gleason at comcast.net wrote:
If anyone out there is hankering to have one, a DEC PRO telephone Voice Unit is on Ebay right now.
http://www.ebay.com/itm/NASA-Digital-DEC-DTC11-B-Voice-Unit-Professional-30…
If anyone out there is hankering to have one, a DEC PRO telephone Voice Unit is on Ebay right now.
http://www.ebay.com/itm/NASA-Digital-DEC-DTC11-B-Voice-Unit-Professional-30…
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
From: "Billquist, Johnny" <bqt at softjar.se>
To: "hecnet" <hecnet at Update.UU.SE>
Sent: Tuesday, May 20, 2014 10:52:04 AM
Subject: Re: QBUS sound [Was: Re: [HECnet] Parallel computing using DECnet]
On 2014-05-20 17:39, Jean-Yves Bernier wrote:
> At 8:05 AM +0200 2/5/14, Pontus Pihlgren wrote:
>
>> I've yet to see a PDP-11 with builtin color graphics _and_ sound.
>
>
> This one has both:
> http://www2.pescadoo.net/pdp/syter/grm2082.jpg
>
> The machine is a SMS 1000 OEM 11/73.
>
> Here is the mixer screen:
> http://www2.pescadoo.net/pdp/syter/INSTR2.GRA.png
>
> and the edit screen:
> http://www2.pescadoo.net/pdp/syter/INSTR5.GRA.png
>
>
> 512x512x8 frame buffer manufactured by Arinfo, France.
>
> Serial BitPad.
>
> Custom 4AD/8DA through DRV11.
>
>
> Discontinued.
Of course... :-(
Anyway, I just realized/remembered that I'm not sure if the PRO was ever
mentioned in the context of PDP-11 with graphics and sound.
The PRO obviously always have grahpics. But there was also a sound
option to it, which could interface with telephone systems. Not sure
exactly how capable it was, but I have some blurb in a handbook somewhere.
Johnny
On 2014-05-20 18:04, Gregg Levine wrote:
Hello!
It's strange. I think I've seen a PRO someplace, but I can't recall
where. I do recall seeing a PDP-11 working in special circumstances.
(Would anyone curious please ask off list.)
Would a board built to be a MIDI controller suffice? One of the
composers who specializes in TV music basically constructed a whole
system for a TV show about thirty years ago. Eventually he switched to
a Mac.......
Well, I have a PRO-380. But I don't have any sound on mine...
I just know that there was at least the TMS system, which interfaced to the telephones. It could also produce general sounds, if I remember right.
There might have been some other sound system as well, but I would have to check.
Johnny
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Tue, May 20, 2014 at 11:52 AM, Johnny Billquist <bqt at softjar.se> wrote:
On 2014-05-20 17:39, Jean-Yves Bernier wrote:
At 8:05 AM +0200 2/5/14, Pontus Pihlgren wrote:
I've yet to see a PDP-11 with builtin color graphics _and_ sound.
This one has both:
http://www2.pescadoo.net/pdp/syter/grm2082.jpg
The machine is a SMS 1000 OEM 11/73.
Here is the mixer screen:
http://www2.pescadoo.net/pdp/syter/INSTR2.GRA.png
and the edit screen:
http://www2.pescadoo.net/pdp/syter/INSTR5.GRA.png
512x512x8 frame buffer manufactured by Arinfo, France.
Serial BitPad.
Custom 4AD/8DA through DRV11.
Discontinued.
Of course... :-(
Anyway, I just realized/remembered that I'm not sure if the PRO was ever
mentioned in the context of PDP-11 with graphics and sound.
The PRO obviously always have grahpics. But there was also a sound option to
it, which could interface with telephone systems. Not sure exactly how
capable it was, but I have some blurb in a handbook somewhere.
Johnny
Hello!
It's strange. I think I've seen a PRO someplace, but I can't recall
where. I do recall seeing a PDP-11 working in special circumstances.
(Would anyone curious please ask off list.)
Would a board built to be a MIDI controller suffice? One of the
composers who specializes in TV music basically constructed a whole
system for a TV show about thirty years ago. Eventually he switched to
a Mac.......
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Tue, May 20, 2014 at 11:52 AM, Johnny Billquist <bqt at softjar.se> wrote:
On 2014-05-20 17:39, Jean-Yves Bernier wrote:
At 8:05 AM +0200 2/5/14, Pontus Pihlgren wrote:
I've yet to see a PDP-11 with builtin color graphics _and_ sound.
This one has both:
http://www2.pescadoo.net/pdp/syter/grm2082.jpg
The machine is a SMS 1000 OEM 11/73.
Here is the mixer screen:
http://www2.pescadoo.net/pdp/syter/INSTR2.GRA.png
and the edit screen:
http://www2.pescadoo.net/pdp/syter/INSTR5.GRA.png
512x512x8 frame buffer manufactured by Arinfo, France.
Serial BitPad.
Custom 4AD/8DA through DRV11.
Discontinued.
Of course... :-(
Anyway, I just realized/remembered that I'm not sure if the PRO was ever
mentioned in the context of PDP-11 with graphics and sound.
The PRO obviously always have grahpics. But there was also a sound option to
it, which could interface with telephone systems. Not sure exactly how
capable it was, but I have some blurb in a handbook somewhere.
Johnny
On 2014-05-20 17:39, Jean-Yves Bernier wrote:
At 8:05 AM +0200 2/5/14, Pontus Pihlgren wrote:
I've yet to see a PDP-11 with builtin color graphics _and_ sound.
This one has both:
http://www2.pescadoo.net/pdp/syter/grm2082.jpg
The machine is a SMS 1000 OEM 11/73.
Here is the mixer screen:
http://www2.pescadoo.net/pdp/syter/INSTR2.GRA.png
and the edit screen:
http://www2.pescadoo.net/pdp/syter/INSTR5.GRA.png
512x512x8 frame buffer manufactured by Arinfo, France.
Serial BitPad.
Custom 4AD/8DA through DRV11.
Discontinued.
Of course... :-(
Anyway, I just realized/remembered that I'm not sure if the PRO was ever mentioned in the context of PDP-11 with graphics and sound.
The PRO obviously always have grahpics. But there was also a sound option to it, which could interface with telephone systems. Not sure exactly how capable it was, but I have some blurb in a handbook somewhere.
Johnny
On Tue, 20 May 2014, Johnny Billquist wrote:
It's a dual-height board. I don't think it /can/ be an 11/23+!
Doh! So you actually have a KDF11-AA (M8186). That sucks. I'm not sure if those were ever upgraded to 22-bit addressing, or if you need the KDF11-BA (M8189) for that.
Not sure. Not going to complaing considering the price. ;)
Oh well, so you might actually be stuck with 11M then.
Yeah. :(
My 11/23+ board is dead++ but I have a replacement (eventually) on the way.
Hey, at least I can run mapped unlike my 11/03s. ;) I have a lot of those boards...
I'm tired and I've been fiddling with many different things. ;)
:-)
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-20 17:11, Cory Smelosky wrote:
On Tue, 20 May 2014, Johnny Billquist wrote:
My memory board is third-party. Looks like it's truncating my memory
then. ;)
Are you sure. Very few 11/23 systems actually exist. Most people
really have 11/23+ systems, even if they are not aware of it.
It's a dual-height board. I don't think it /can/ be an 11/23+!
Doh! So you actually have a KDF11-AA (M8186). That sucks. I'm not sure if those were ever upgraded to 22-bit addressing, or if you need the KDF11-BA (M8189) for that.
Oh well, so you might actually be stuck with 11M then.
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few
things running, not much pool is needed.
Ahh. I must be thinking of...buffer space?
Not sure what you are thinking of. :-)
I'm tired and I've been fiddling with many different things. ;)
:-)
Johnny
On Tue, 20 May 2014, Paul_Koning at Dell.com wrote:
The disk is 1048778 blocks. I created a 512M image and copied it bit-for-bit to the disk. I think i'll just go SYSGEN 4.8 and wait for my cleaning tapes to get RSTS/E working.
How about copying the image back off, to see if the disk controller mangled it?
I'll do that once RSX is up so I don't have to dismantle the system again. ;)
The message you quoted says that the content of block 1 is invalid (the pack label). Judging by the code, what it found is 0143161 rather than a valid PCS.
Interesting. I wonder how its getting mangled. The disk size IS changing between copy and creation, though. (Because both are different...apparently unavoidable due to 1000 versus 1024k.)
I wonder if your partitioning disk controller is misbehaving.
Possible...but RT-11 and RSX-11 are fine with it. They're a bit less picky though. VMS didn't seem too picky, either.
BTW, sufficiently recent versions of RSTS (including the one you have, given that message) should handle a 2 GB disk directly (at DCS=64). That way you don t need to mess with partitions.
I didn't have a tape drive at the time...so I would've needed to copy a 2G image at 10Mbit to a disk that wouldn't show up as 2G. (That drive then failed)
I'll just wait for the cleaning tape.
paul
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On May 20, 2014, at 10:58 AM, Cory Smelosky <b4 at gewt.net> wrote:
On Tue, 20 May 2014, Cory Smelosky wrote:
After a reboot:
Pack cluster size is not 1, 2, 4, 8, 16, 32 or 64.
PC=120324 PS=030344 OV=000006 M5=004000 M6=004200 SP=041236
R0=000026 R1=143161 R2=143161 R3=000000 R4=000002 R5=041350
The disk is 1048778 blocks. I created a 512M image and copied it bit-for-bit to the disk. I think i'll just go SYSGEN 4.8 and wait for my cleaning tapes to get RSTS/E working.
How about copying the image back off, to see if the disk controller mangled it?
The message you quoted says that the content of block 1 is invalid (the pack label). Judging by the code, what it found is 0143161 rather than a valid PCS.
I wonder if your partitioning disk controller is misbehaving.
BTW, sufficiently recent versions of RSTS (including the one you have, given that message) should handle a 2 GB disk directly (at DCS=64). That way you don t need to mess with partitions.
paul
On Tue, 20 May 2014, Johnny Billquist wrote:
My memory board is third-party. Looks like it's truncating my memory
then. ;)
Are you sure. Very few 11/23 systems actually exist. Most people really have 11/23+ systems, even if they are not aware of it.
It's a dual-height board. I don't think it /can/ be an 11/23+!
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few
things running, not much pool is needed.
Ahh. I must be thinking of...buffer space?
Not sure what you are thinking of. :-)
I'm tired and I've been fiddling with many different things. ;)
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-20 17:06, Cory Smelosky wrote:
On Tue, 20 May 2014, Johnny Billquist wrote:
4.6M+'s SYSGEN and it wouldn't accept 11/23 as an answer.
The difference between the 11/23 and 11/23+ is the amount of memory.
The original 11/23 could not go above 256K... If you have more, then
you actually have an 11/23+.
My memory board is third-party. Looks like it's truncating my memory
then. ;)
Are you sure. Very few 11/23 systems actually exist. Most people really have 11/23+ systems, even if they are not aware of it.
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few
things running, not much pool is needed.
Ahh. I must be thinking of...buffer space?
Not sure what you are thinking of. :-)
Johnny
On Tue, 20 May 2014, Johnny Billquist wrote:
4.6M+'s SYSGEN and it wouldn't accept 11/23 as an answer.
The difference between the 11/23 and 11/23+ is the amount of memory. The original 11/23 could not go above 256K... If you have more, then you actually have an 11/23+.
My memory board is third-party. Looks like it's truncating my memory then. ;)
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few things running, not much pool is needed.
Ahh. I must be thinking of...buffer space?
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-20 17:01, Cory Smelosky wrote:
On Tue, 20 May 2014, Johnny Billquist wrote:
M+ do not need split I/D-space. But you do need 512K of memory. But
the 11/23 and 11/24 are supported CPUs.
I have 1M of memory.
Sure you're not confusing the 11/23 with the 11/23+? I was poking at
4.6M+'s SYSGEN and it wouldn't accept 11/23 as an answer.
The difference between the 11/23 and 11/23+ is the amount of memory. The original 11/23 could not go above 256K... If you have more, then you actually have an 11/23+.
(That said, without split I/D-space, you'll have preciously little
pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Pool space is used for many things, but with just one user, and few things running, not much pool is needed.
Johnny
Hans Vlems asks: What's wrong with it?
I have had a number of Exabyte units over the years on UNIX systems. I still have at least one of each 8200 and 8500. I always found them to be reliable and if you used data style cartridges (not the video ones) very reliable and the standard BSD tape utilities and drivers support them. The biggest issue I had with them is feeding them: when writing to them, they can consume data faster than many applications can source it and "data late" caused "bad things" to happen on the tape firmware. For UNIX, years before I had written a program called double DD which was modeled after a program of the same name from Europe (the original was two cooperating processes that hand off control back and forth over a pipe]. My version used multiple threads to over lap the I/O and thus reduce if not remove the data late errors. [I used to the same program for QIC tapes too on the Sun systems we had].
So a tar command line would look like:
tar cvf - . | ddd ibs=20b obs=256K of=/dev/rmt0
Clem
On Tue, 20 May 2014, Johnny Billquist wrote:
M+ do not need split I/D-space. But you do need 512K of memory. But the 11/23 and 11/24 are supported CPUs.
I have 1M of memory.
Sure you're not confusing the 11/23 with the 11/23+? I was poking at 4.6M+'s SYSGEN and it wouldn't accept 11/23 as an answer.
(That said, without split I/D-space, you'll have preciously little pool space, but that might not be a big issue for you right here.)
Probably not. I'll only have one disk in use at a time really.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Tue, 20 May 2014, Cory Smelosky wrote:
After a reboot:
Pack cluster size is not 1, 2, 4, 8, 16, 32 or 64.
PC=120324 PS=030344 OV=000006 M5=004000 M6=004200 SP=041236
R0=000026 R1=143161 R2=143161 R3=000000 R4=000002 R5=041350
The disk is 1048778 blocks. I created a 512M image and copied it bit-for-bit to the disk. I think i'll just go SYSGEN 4.8 and wait for my cleaning tapes to get RSTS/E working.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-20 15:14, Cory Smelosky wrote:
On Tue, 20 May 2014, Jordi Guillaumes i Pons wrote:
El 20/05/2014, a les 14.33, Cory Smelosky <b4 at gewt.net> va escriure:
Back to trying RSX-11M 4.8. That's 100M and doubtful it'll complain.
Unless you want to feel the pain (or the joy) of manually defining
memory partitions, I'd suggest you to go PLUS :)
Can't! No Split I&D.
M+ do not need split I/D-space. But you do need 512K of memory. But the 11/23 and 11/24 are supported CPUs.
(That said, without split I/D-space, you'll have preciously little pool space, but that might not be a big issue for you right here.)
Johnny
On Tue, 20 May 2014, Paul_Koning at Dell.com wrote:
Could you explain what you wanted to do, what steps you followed, and what exactly the trouble is?
I staged RSTS/E in SIMH before copying its disk image to the real PDP-11/23.
It kept complaining about the pack size and whatnot...but I think I might have finally made progress.
BOOT DU1 . ARE YOU SURE? yes
WAIT...
?
?RU0: timeout during initialization, step 000003 - device disabled.
RU0: failed during units lookup - device disabled.
Fatal RSTS/E system initialization error!
Disk DU1: is hung
PC=120400 PS=030340 OV=000006 M5=004000 M6=004200 SP=041236
R0=000001 R1=000026 R2=042125 R3=000016 R4=000001 R5=041350
Progress!
If you feed a disk to RSTS that doesn t have a RSTS file system on it, it will get confused/annoyed. The error message you quoted is an example of what you would see.
Ahhhhh. I see. I was copying the disk incorrectly then.
Given an uninitialized disk, you use the disk initialization procedure (from INIT or online). The dialog you showed does that. After that procedure, you ll have a RSTS format disk.
Okay.
Partitioning? RSTS doesn t have partitions. The whole physical drive is a single file system. It also doesn t depend on NVRAM (PDP11s traditionally have none).
My controller is splitting a 2G drive in to 4 ~500M drives. It appears the config is stored in its NVRAM.
Block 0 is the boot block (dummy not bootable boot block by default). Boot 1 is the superblock ( pack label ). For new (V9 or later) disks that points to the MFD (top level directory); for old disks (format 0.0) it is the first block of the [1,1] directory which doubles as MFD on that layout.
paul
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On May 20, 2014, at 8:33 AM, Cory Smelosky <b4 at gewt.net> wrote:
So:
Pack cluster size is not 1, 2, 4, 8, 16, 32 or 64.
PC=120324 PS=030344 OV=000006 M5=004000 M6=004200 SP=041240
R0=000026 R1=143161 R2=143161 R3=000000 R4=000000 R5=041350
The disk should be around ~512M. I created a 500M disk.
Disk? DU0
Pack ID? 0
Pack cluster size <16>?
MFD cluster size <16>?
SATT.SYS base <30530>?
Pre-extend directories <NO>?
PUB, PRI, or SYS <SYS>?
[1,1] cluster size <16>?
[1,2] cluster size <16>?
[1,1] and [1,2] account base <30530>?
Date last modified <YES>?
New files first <NO>?
Read-only <NO>?
Patterns <3>? 0
Erase Disk <YES>? YES
Proceed (Y or N)? Y
Unless the partitioning is written to the first block and not done through controller NVRAM...I can't see the reasoning.
Could you explain what you wanted to do, what steps you followed, and what exactly the trouble is?
If you feed a disk to RSTS that doesn t have a RSTS file system on it, it will get confused/annoyed. The error message you quoted is an example of what you would see.
Given an uninitialized disk, you use the disk initialization procedure (from INIT or online). The dialog you showed does that. After that procedure, you ll have a RSTS format disk.
Partitioning? RSTS doesn t have partitions. The whole physical drive is a single file system. It also doesn t depend on NVRAM (PDP11s traditionally have none).
Block 0 is the boot block (dummy not bootable boot block by default). Boot 1 is the superblock ( pack label ). For new (V9 or later) disks that points to the MFD (top level directory); for old disks (format 0.0) it is the first block of the [1,1] directory which doubles as MFD on that layout.
paul
El 20/05/2014, a les 15.25, Cory Smelosky <b4 at gewt.net> va escriure:
Going to fight RSTS/E first. I can succeed if I image with a VAX. ;)
Thanks! What kit did you use for 4.8 non-plus?
I've got several tape images named "decnet11something" around. I guess its the one named "decnet11m48", but I'm not completely sure about that.
And, yes, I'm a disaster.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES