Installation of 3.0 EA2 on 12.1.0.2

Question

I've got an existing 12.1.0.2 db (non-pdb), vanilla install, so apex 4.2 within it.
I downloaded 3.0 EA2 and ran through the install.
When I start it, I see sessions on the database for APEX_LISTENER, ORDS_PUBLIC_USER
but when I got to http://myhost:xxx/ords, I get a "ORACLE REST DATA SERVICES" banner page but it just contains "404 Not found"
Startup log below - but have I missed anything obvious ?
C:\Oracle\ords>java -jar ords.war
Verify ORDS schema in Database Configuration apex
Mar 12, 2015 3:19:53 PM oracle.dbtools.rt.config.setup.SchemaSetup install
INFO: Oracle REST Data Services schema version 3.0.0.65.09.31
2015-03-12 15:19:53.413:INFO::main: Logging initialized @2034ms
2015-03-12 15:19:53.909:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
2015-03-12 15:19:53.918:INFO:oejsh.ContextHandler:main: Started o.e.j.s.h.ContextHandler@7a1ebcd8{/i,null,AVAILABLE}
Mar 12, 2015 3:19:54 PM oracle.json.ords.SodaShared startup
INFO: Starting up ORDS JSON service
2015-03-12 15:19:54.007:INFO:/ords:main: INFO: Using configuration folder: C:\Oracle\ords\_conf\ords
2015-03-12 15:19:54.008:INFO:/ords:main: FINEST: |ApplicationContext [configurationFolder=C:\Oracle\ords\_conf\ords, services=Application Scope]|
Mar 12, 2015 3:19:54 PM oracle.dbtools.common.config.db.DatabasePools validatePool
INFO: Validating pool: apex_al
Mar 12, 2015 3:19:54 PM oracle.dbtools.common.config.db.DatabasePools validatePool
INFO: Pool: apex_al is correctly configured
Mar 12, 2015 3:19:54 PM oracle.dbtools.common.config.db.DatabasePools validatePool
INFO: Validating pool: apex_pu
Mar 12, 2015 3:19:54 PM oracle.dbtools.common.config.db.DatabasePools validatePool
INFO: Pool: apex_pu is correctly configured
Mar 12, 2015 3:19:54 PM oracle.dbtools.common.config.db.DatabasePools validatePool
INFO: Validating pool: apex_rt
Mar 12, 2015 3:19:54 PM oracle.dbtools.common.config.db.DatabasePools validatePool
INFO: Pool: apex_rt is correctly configured
2015-03-12 15:19:54.276:INFO:/ords:main: INFO: Oracle REST Data Services initialized|Oracle REST Data Services version : 3.0.0.65.09.31|Oracle REST Data Services server info: jetty
/9.2.z-SNAPSHOT|
2015-03-12 15:19:54.278:INFO:oejsh.ContextHandler:main: Started o.e.j.s.ServletContextHandler@528931cf{/ords,null,AVAILABLE}
2015-03-12 15:19:54.382:INFO:oejs.ServerConnector:main: Started ServerConnector@15bfd87{HTTP/1.1}{0.0.0.0:8080}
2015-03-12 15:19:54.383:INFO:oejs.Server:main: Started @3006ms
Mar 12, 2015 3:20:14 PM oracle.dbtools.common.config.db.DatabasePools createPool
INFO: Configuration properties for: apex_pu
Mar 12, 2015 3:20:14 PM oracle.dbtools.common.config.db.DatabasePools listConfiguration
INFO: cache.caching=false
cache.directory=/tmp/apex/cache
cache.duration=days
cache.expiration=7
cache.maxEntries=500
cache.monitorInterval=60
cache.procedureNameList=
cache.type=lru
db.hostname=xxxxx
db.port=1521
db.servicename=np12
debug.debugger=false
debug.printDebugToScreen=false
error.keepErrorMessages=true
error.maxEntries=50
jdbc.DriverType=thin
jdbc.InactivityTimeout=1800
jdbc.InitialLimit=3
jdbc.MaxConnectionReuseCount=1000
jdbc.MaxLimit=10
jdbc.MaxStatementsLimit=10
jdbc.MinLimit=1
jdbc.statementTimeout=900
log.logging=true
log.maxEntries=5000
misc.compress=
misc.defaultPage=apex
security.crypto.enc.password=******
security.crypto.mac.password=******
security.disableDefaultExclusionList=false
security.maxEntries=2000
db.password=******
db.username=ORDS_PUBLIC_USER
Mar 12, 2015 3:20:14 PM oracle.dbtools.common.config.db.ConfigurationValues log
WARNING: *** jdbc.MaxLimit in configuration apex_pu is using a value of 10, this setting may not be sized adequately for a production environment ***
Mar 12, 2015 3:20:14 PM oracle.dbtools.common.config.db.ConfigurationValues log
WARNING: *** jdbc.InitialLimit in configuration apex_pu is using a value of 3, this setting may not be sized adequately for a production environment ***
Mar 12, 2015 3:20:14 PM oracle.ucp.common.UniversalConnectionPoolBase initInactiveConnectionTimeoutTimer
INFO: inactive connection timeout timer scheduled
Mar 12, 2015 3:20:14 PM oracle.dbtools.common.config.db.DatabasePools createPool
INFO: Configuration properties for: apex_al
Mar 12, 2015 3:20:14 PM oracle.dbtools.common.config.db.DatabasePools listConfiguration
INFO: cache.caching=false
cache.directory=/tmp/apex/cache
cache.duration=days
cache.expiration=7
cache.maxEntries=500
cache.monitorInterval=60
cache.procedureNameList=
cache.type=lru
db.hostname=xxxxx
db.port=1521
db.servicename=np12
debug.debugger=false
debug.printDebugToScreen=false
error.keepErrorMessages=true
error.maxEntries=50
jdbc.DriverType=thin
jdbc.InactivityTimeout=1800
jdbc.InitialLimit=3
jdbc.MaxConnectionReuseCount=1000
jdbc.MaxLimit=10
jdbc.MaxStatementsLimit=10
jdbc.MinLimit=1
jdbc.statementTimeout=900
log.logging=true
log.maxEntries=500
misc.compress=
misc.defaultPage=apex
security.crypto.enc.password=******
security.crypto.mac.password=******
security.disableDefaultExclusionList=false
security.maxEntries=2000
db.password=******
db.username=APEX_LISTENER
Mar 12, 2015 3:20:14 PM oracle.dbtools.common.config.db.ConfigurationValues log
WARNING: *** jdbc.MaxLimit in configuration apex_al is using a value of 10, this setting may not be sized adequately for a production environment ***
Mar 12, 2015 3:20:14 PM oracle.dbtools.common.config.db.ConfigurationValues log
WARNING: *** jdbc.InitialLimit in configuration apex_al is using a value of 3, this setting may not be sized adequately for a production environment ***
Mar 12, 2015 3:20:14 PM oracle.ucp.common.UniversalConnectionPoolBase initInactiveConnectionTimeoutTimer
INFO: inactive connection timeout timer scheduled

Answer 1

The script adds "/apex/images" to the the directory name you pass as a parameter.
So, if the images are in the C:\BACKUP\APEX\images directory, you should try using just C:\BACKUP as the parameter.
It uses this command:
create directory APEX_IMAGES as '&1/apex/images';