Error codes
Find the meaning, causes and steps for LuvMacro error codes.
File loading and compatibility
- LM-1001 — Unable to Open Macro
The file couldn't be found.
- LM-1002 — Unable to Open Macro
The system wouldn't let LuvMacro read the file.
- LM-1003 — Unable to Open Macro
The file couldn't be read.
- LM-1004 — Unable to Open Macro
This isn't a LuvMacro file.
- LM-1005 — Unable to Open Macro
This looks like a recording from another macro program, which LuvMacro can't open.
- LM-1006 — Unable to Open Macro
This file is a different kind of file, not a macro.
- LM-1007 — Unable to Open Macro
The file is larger than any LuvMacro macro can be.
- LM-1008 — Unable to Open Macro
The file is empty.
- LM-1009 — Unable to Open Macro
The file is damaged, so LuvMacro can't read it.
- LM-1010 — Unable to Open Macro
The file is incomplete. It ends before the macro does.
- LM-1011 — Unable to Open Macro
This macro was saved by a newer version of LuvMacro.
- LM-1012 — Unable to Open Macro
Part of the macro's information is missing or isn't valid.
- LM-1013 — Unable to Open Macro
The macro has more events than LuvMacro can open.
- LM-1014 — Unable to Open Macro
There isn't enough free memory to open this file.
- LM-1015 — Unable to Open Macro
The macro's timing doesn't add up.
Playback
- LM-2001 — Playback Problem
There is nothing to play yet.
- LM-2002 — Playback Problem
Playback is off because the emergency-stop shortcut isn't working.
- LM-2003 — Playback Problem
Playback didn't start because no other window was in front.
- LM-2004 — Playback Problem
Playback stopped because the window was closed or minimized.
- LM-2005 — Playback Problem
Playback stopped because a different window came to the front.
- LM-2006 — Playback Problem
Playback stopped because the system refused an input.
- LM-2007 — Playback Problem
Some keys or buttons couldn't be released after playback.
- LM-2008 — Playback Problem
LuvMacro couldn't read the size of your window, so clicks may not land in the right places.
- LM-2009 — Playback Problem
Your window is a different shape from the recording.
Recording and saving
- LM-3001 — Recording Problem
Recording didn't start because no other window was in front.
- LM-3002 — Recording Problem
Recording couldn't start.
- LM-3003 — Recording Problem
Nothing was recorded.
- LM-3004 — Recording Problem
The recording reached its size limit, so the end was cut off.
- LM-3005 — Recording Problem
The window moved or changed size while recording.
- LM-3010 — Unable to Save Macro
The system wouldn't let LuvMacro save the macro there.
- LM-3011 — Unable to Save Macro
There isn't enough free space to save the macro.
- LM-3012 — Unable to Save Macro
That folder couldn't be found.
- LM-3013 — Unable to Save Macro
The macro couldn't be saved.
Updates
- LM-4001 — Update Problem
LuvMacro couldn't reach the update server.
- LM-4002 — Update Problem
The update information wasn't valid, so it was ignored.
- LM-4003 — Update Problem
The update couldn't be downloaded.
- LM-4004 — Update Problem
The downloaded update didn't pass LuvMacro's safety check, so it was thrown away.
- LM-4005 — Update Problem
The update was downloaded, but the installer couldn't be started.
- LM-4006 — Update Problem
This copy of LuvMacro can't update itself.
- LM-4007 — Update Problem
No update information was found.
System and permissions
- LM-5001 — Permission Needed
The system hasn't given LuvMacro the permission it needs.
- LM-5002 — Settings Problem
Your settings file was damaged or had values that aren't valid.
- LM-5003 — Shortcut Problem
A shortcut couldn't be set up.
- LM-5004 — Couldn't Open Link
LuvMacro couldn't open your web browser.
- LM-5005 — Settings Not Saved
The change is active for now, but couldn't be saved to disk.
- LM-5006 — Data Folder Problem
LuvMacro couldn't use its data folder.
- LM-5007 — Log Problem
LuvMacro couldn't write its diagnostic log.
- LM-5008 — Low Disk Space
The drive that holds LuvMacro's data is almost full.
Unexpected failures
- LM-9001 — Something Went Wrong
LuvMacro hit a problem it didn't expect.
- LM-9002 — Something Went Wrong
A task running in the background hit a problem it didn't expect.
